Write one page for each brand-and-fault pairing you really fix, from a fact sheet built out of your own job records, and send the same review request to every customer once the repair is confirmed working. AI drafts both; you supply the facts and check the wording against Google's spam and review rules.
Pages that swap a brand name or an area name into the same paragraph are what Google's spam policies call doorway abuse and scaled content abuse, and AI makes them cheap to produce at exactly the wrong scale. The test is whether many pages add value for users, not how they were made. So the plan below is small: a handful of pages that each contain something a competitor's template cannot, and a review routine that asks everybody for the same thing in the same way.
How many brand-and-fault pages your jobs can honestly support
Export last year's completed jobs and paste only the free-text columns (what the customer reported, what the technician did) into an assistant, with names and addresses removed. Ask it to tag each job with brand, appliance and fault, and to write "unclear" rather than guess. Here is the kind of tidy-up to expect from messy notes:
| Free-text job note (names removed) | Brand | Appliance | Fault |
|---|---|---|---|
| washer wont drain, pump jammed with hairgrip, replaced pump | Brand A | Washing machine | Not draining (pump) |
| fridge warm, defrost heater failed | Brand B | Fridge-freezer | Not cooling (defrost) |
| dryer runs cold, element open circuit | Brand C | Tumble dryer | Not heating |
| noise on spin?? no fault found, customer to call back | Unclear | Washing machine | Unclear |
The fourth row is the one to keep. When a note does not say, the tag says "unclear" and the row stays out of the counts, so a guess never becomes a page. Then count. Here is what a two-person firm with two vans and 640 completed jobs might see, with brands left as letters so nobody is named:
| Brand and appliance | Fault | Jobs in 12 months | Usable photos | Page? |
|---|---|---|---|---|
| Brand A washing machine | Not draining (pump or blockage) | 31 | Yes | Yes |
| Brand B fridge-freezer | Not cooling (defrost fault) | 24 | Yes | Yes |
| Brand B dishwasher | Not draining | 19 | No | After two photos |
| Brand C tumble dryer | Not heating | 17 | Yes | Yes |
| Brand A washing machine | Door lock fault | 14 | Yes | Yes |
| Brand C oven | Control board | 9 | Yes | Yes |
| Brand D washing machine | Leak from the door seal | 6 | Yes | Yes |
| Brand E dishwasher | Leak | 4 | No | No |
| Brand F cooker hood | Motor | 2 | No | No |
| Every other combination | Under four jobs each | 514 | n/a | No |
The threshold I'd use is my own, not Google's: a page earns its place when you have fixed that brand and fault at least five times in the year and hold at least two photos you can use. That gives six pages now and a seventh once someone photographs a blocked dishwasher pump. The other 514 jobs are a long tail, and writing a thin page for each is exactly the pattern the spam policy describes: many pages generated without adding value for users. Serve the tail with one general page that lists the appliances and brands you repair, the faults you see most, how to book and your repair-or-replace rule, and links to the fault pages above. That is also the page that carries your service area.
Notice what is absent: area names. Google's doorway abuse definition includes pages created for specific, similar queries and pages targeted at particular regions or cities that funnel people to one destination. Put your service area on one page and in your Business Profile, and mention it in one sentence on each fault page. The tutorial on service-area pages without duplicate content goes into that side of the problem, and the one on a Google Business Profile for a heating and cooling firm shows how to handle areas inside the profile.
One general page for the long tail of brands and faults
The long tail of more than 500 jobs that never earn their own page still needs somewhere to land, and the general page is where an assistant's habit of padding does the most damage, because it has the least to work from. Build it from a count rather than a wish list. Ask the assistant to group last year's jobs by appliance and list every brand with at least one completed repair, then check the list yourself: a brand you fixed once, three years ago, does not belong. A filled-in block for the two-van firm might read:
We repair washing machines, dishwashers, tumble dryers, fridge-freezers, ovens and cooker hoods. Last year we completed 640 repairs, most often for drains and pumps, door locks, heating elements, defrost faults and control boards, and the most common of those have their own pages below. Brands we repaired last year: [brands from your count]. We do not repair commercial machines or gas appliances. If a repair is not worth doing, we will tell you, and our repair-or-replace rule is set out on this page.
The sentence that matters most is the exclusion. Left alone, an assistant writes "we repair all makes and models", which is rarely true and brings calls you will turn away. Saying what you do not repair saves those calls and makes the rest of the page believable. The general page is also the one place for the full service area; each fault page gets one sentence that links to it.
A fact sheet per page, built from your own jobs
The fact sheet is what stops the assistant filling a page with the generic claims every competitor's page makes. Each field is something only your records can supply. Here is the sheet for the first page, filled in (the counts and prices are illustrative):
| Field | Entry for [Brand] washing machine not draining |
|---|---|
| What customers report | "Won't drain", "water left in the drum", "stops mid-cycle", error code [code] |
| What we found, from our own jobs | 31 jobs last year: 12 blocked filter or hose, 15 failed pump, 4 other (wiring or control board) |
| What we check, in order | Filter housing, drain hose, pump for debris and noise, then wiring and board |
| Typical repair and price range | Filter or hose clear: $85 to $110. Pump replacement: $145 to $210, parts and labour (from our invoices) |
| Parts | Genuine pump, usually delivered next day; compatible pump available on request |
| Typical time on site | 45 to 75 minutes |
| When we recommend replacing | Repair over half the price of a comparable new machine and machine at or past 8 years |
| What a customer can safely try first | Switch off and unplug; check and clean the filter as the manual describes; nothing else |
| Warranty | 90 days on the replaced part and our labour |
| Photos (with permission) | Pump removed from a job, with debris; filter housing before and after |
| Service area | One sentence linking to the service-area page |
| Reviewed by | [technician's first name], checked on [date] |
The "safely try first" row deserves care. Assistants love to add do-it-yourself steps, and a page that tells readers to open a machine involving water and mains electricity is one you do not want to be wrong. Include only the steps your technicians would give over the phone, and put the safety line first. For anything involving gas, give no home steps at all.
The "reviewed by" row is not decoration. Google's guidance on helpful content asks whether someone who demonstrably knows the topic wrote or reviewed a page, and it flags using generative AI to produce large amounts of text without manual oversight as little effort. Have the technician who actually does this repair read each draft, correct it and put their first name and the date on it.
Thin page and useful page, side by side
This is the template page that comes out when nobody supplies facts:
Appliance Repair in [Area]. We repair [Brand] washing machines in [Area] and nearby. Our friendly, experienced engineers offer fast, affordable service. Call us today!
And this is the top of the page the fact sheet produces:
[Brand] washing machine not draining: what we find and what it costs
In the 31 [Brand] washing machine drain faults we repaired last year, 12 were a blocked filter or hose, 15 were a failed pump and 4 were something else, such as wiring or the control board. A blocked filter or hose is usually an $85 to $110 visit. A pump replacement is usually $145 to $210, parts and labour. If your machine is eight years old or more and the repair would cost more than half the price of a new one, we will tell you so and let you decide.
The second version works as an answer on its own, which matters because a reader who stops after those lines still gets what they came for. It also holds information that exists nowhere else: your counts, your ranges, your rule. The rest of the page follows a fixed order. A short answer first. What we usually find, with counts. What we check, in order. What the repair involves and costs. When we would recommend replacing instead. What you can safely try first. How to book, including a request for a photo of the rating plate. Then the photos with captions, a link to the service-area page, and links to the other fault pages for the same brand.
The page prompt, one draft and five claims to remove
Write a page for a repair firm's website about [brand] [appliance] [fault].
Use only the fact sheet below. Do not add claims about authorisation,
certification, speed of service, coverage or statistics that are not in it.
Do not mention any town or area. Do not add repair steps for the customer
beyond the ones listed under "safely try first".
Structure: a 50 to 70 word short answer using our own counts; what we usually
find; what we check; the repair and price range; when we would recommend
replacing instead (apply the rule); what to try first; how to book.
Plain, calm, no exclamation marks, no urgency.
Fact sheet: [paste]Given that prompt, an assistant still tends to wander. A typical first draft, with the problems numbered:
[Brand] washing machine not draining? We are an authorised [Brand] repair centre (1) covering the whole region with same-day visits (2). Our friendly, certified engineers (3) fix this fault every day. Most drain pump failures happen after seven years (4). To fix it yourself, remove the pump cover and clear the impeller with a screwdriver (5). Call us today!
- Authorisation. Not in the fact sheet. "Authorised" is something a brand grants, so if you are not, the claim is simply false.
- Same-day, whole region. Your records show next-day appointments in a defined area. Unsupported speed claims are what readers quote back.
- "Certified". Nothing in the sheet supports it. State a real certification or delete the word.
- A statistic with no source. Replace it with your own counts: 15 failed pumps in 31 jobs.
- Do-it-yourself steps. The sheet allows unplugging and cleaning the filter, nothing more. Remove anything else.
Using a brand's name to say what you repair is ordinary and descriptive. Using its logo, or wording that suggests an official relationship, is something to check against that brand's own terms first.
Repair-or-replace wording that costs a job and wins the next
A repair firm saying "this may not be worth repairing" feels like a loss. It is the sentence that makes the rest of the page believable. Use the same rule on the page that you use in your estimates: more than half the price of a comparable new machine and past your late-life age. The worked estimate with a repair-or-replace rule sets that rule out step by step, so the page and the quote never disagree.
A paragraph in your own voice, with the numbers from your fact sheet, might read: "If the repair is likely to cost more than half the price of a new [appliance] and yours is [eight] years old or more, we will say so and let you decide. The diagnostic fee of [fee] applies either way." Then avoid the scare lines assistants reach for:
| Line an assistant tends to write | What to put instead |
|---|---|
| "Don't risk a flood in your kitchen." | "If water is leaking, switch the machine off and unplug it, then call us." |
| "The cheapest repairs around." | "Our diagnostic fee is [fee]. Typical repairs run from $[low] to $[high]." |
| "We can fix any brand." | List the brands you actually repair. |
| "Repairing is always cheaper than replacing." | "Repair is not always the cheaper choice, and we will tell you when it is not." |
The first row is the only place a warning belongs: a real safety instruction, phrased as an action. The garage door tutorial on honest offers and local pages works through the same discipline in another repair trade.
Review requests: one ask, to everyone, after the fix
Google's review policy is specific, and it limits what a repair firm can do. As of its current wording, businesses may not offer incentives such as payment, discounts or free service in exchange for a review, may not selectively solicit positive reviews, may not discourage or prohibit negative ones, may not set staff quotas for reviews or ask staff to solicit reviews containing specific content, and should not require or pressure people to leave reviews while on the premises. Google's own tips say you can ask customers to follow a Google link or scan a QR code, and that customers must be signed in to a Google account to review.
That shapes the routine. The trigger is the job being closed as completed, which is a fact about the repair rather than about the customer's mood. Everyone with a completed job receives the same request, whether or not they have said they were pleased. A customer whose repair is still open has not had the repair completed, so there is nothing to ask about yet, and a phone call is the right tool. Sending the request the next day, after the technician has confirmed the machine works, is my suggestion rather than Google's guidance. Here are three scripts:
| Channel | Script |
|---|---|
| Text, the day after | Hi [first name], it's [business]. If you have a minute, an honest Google review helps others decide: [link]. Thanks, [your name] |
| Email, the day after | Subject: Your [appliance] repair. Hi [first name], thank you for choosing us. If you would like to share how the repair went, you can leave a Google review here: [link]. You need to be signed in to a Google account. Honest feedback of any kind is welcome. [your name], [business] |
| Card with a QR code, left with the invoice | Thanks for choosing [business]. If you'd like to review the repair on Google, scan this code whenever suits you. You will need to be signed in to a Google account. |
The text is 128 characters before the link and names are merged in, so keep an eye on the total: a 160-character limit applies in the standard alphabet, and Twilio's documentation says characters outside it, curly apostrophes among them, switch the message to an encoding with a much lower limit. Keep apostrophes straight and count after the merge. At the door, the technician's line is "Everything's working; if you'd like to review the repair, we'll text you a link tomorrow, no obligation". That is a mention, not a request made on the premises.
Here are the wordings that look harmless and are not:
| Wording | Why it breaks the policy |
|---|---|
| "Leave us five stars and get $10 off your next repair." | An incentive in exchange for a review. |
| "Please mention [technician's name] in your review." | Asks for specific content, including a staff member's name. |
| A 1-to-10 survey, with the Google link sent only to 9s and 10s. | Selectively soliciting positive reviews. |
| "Each engineer must collect five reviews a month." | A staff quota for reviews. |
| "Can you do it now on your phone while I pack up?" | Pressure to review on the premises. |
| "Unhappy? Email us instead of posting." | Can read as steering unhappy customers away from reviewing, which the policy bars. |
Handle problems separately, with an ordinary "is everything working?" call on the day, which is service, not solicitation. The tutorial on review requests built from job photos shows a way to attach the ask to the work without breaking these rules.
One failure tends to show up in the first month of an automated routine. A job is closed as complete on Tuesday, the machine trips the electrics again on Wednesday, the customer books a call-back, and that evening the automatic request arrives asking how the repair went. The review that follows is about the request as much as the repair. The fix is a rule about job status, not about mood: when a call-back is booked against a job, its pending request is held, and once the call-back is closed as complete, the same standard request goes out whatever the outcome. Every customer still gets one ask, and nobody is asked to review a repair that is not finished.
Review replies that add something true
Google's own review tips advise keeping replies short and honest, answering questions or sharing a helpful update rather than sending everyone the same thank-you, avoiding deals or promotions in replies, never sharing a reviewer's private information and moving complex issues to a phone call or email. An assistant is good at the first draft of that. Give it the review, your facts and these rules.
A three-star review might say the repair was fine but the part took a week to arrive. A first draft of the reply might read: "Thank you for your feedback. We're sorry the part took longer than expected. We would be happy to offer a free diagnostic on your next visit." The last sentence is a promotion in a reply, so it goes. The edited version, using facts you supply, is: "Thank you for telling us. You are right that the part took a week, because the supplier was out of stock, and we should have said so when we booked. We now tell customers the expected delivery before they approve. If you would like to talk it through, call [number]." Replies should add something true, and a person should read each one before it posts; the tutorial on whether to let AI auto-post replies to Google reviews explains why.
A one-star review needs the same care, sooner. Google's tips list responding in a timely manner as advice for negative reviews; how soon is your call. Say a reviewer writes that the technician arrived late and the machine broke down again two days later. Given your job notes, an assistant will often reach for the record: "Our notes show you declined the replacement hose we recommended on [date]." Even if that is true, it puts the customer's job history in a public reply, and Google's tips say never to share a reviewer's private information. The usable version acknowledges what you can confirm and moves the rest to a call: "We're sorry the machine failed again so soon after our visit, and that we arrived after the window we gave you. Please call [number] so we can look at what happened and put it right." The same tips say to acknowledge mistakes without taking responsibility for things outside your control, so if the second fault turns out to be unrelated to the repair, explain that on the call rather than in public.
Measuring pages and asks, and a weekly fifteen minutes
Judge pages and reviews separately, because they fail for different reasons. For pages, look at impressions and clicks per page in Google Search Console after eight to twelve weeks, and ask new callers which page they read. A page with no impressions after a quarter either needs a clearer title or does not deserve to exist, and merging it into the general page is a fine outcome. For reviews, count requests sent, reviews received and the rate between them. If 380 completed jobs produce 46 reviews, that is 12%, and on 640 jobs a year the same rate gives about 77 reviews, roughly six a month. If the rate is lower than you would like, test the timing and the link, never an incentive.
A weekly routine keeps it alive. On Monday, check that every completed job last week received its request and that none of them were skipped by hand. Read new reviews and reply. Add one new job note to a fact sheet while it is fresh.
Questions appliance repairers ask about pages and reviews
How often should brand-and-fault pages be updated?
Refresh the job counts and price ranges every quarter, and put the date on the page. Re-read each page once a year with the technician who knows the fault, and delete any page for a brand or appliance you no longer repair. A stale price range does more harm than none. If a page has had no impressions after three months of data, merge it into a broader page or retire it.
Should I add FAQ markup to these pages?
Only if you want to, and not in the hope of a rich result: Google's Search Central changelog says the FAQ rich result stopped appearing in Search on 7 May 2026, and its documentation has since been removed. Question-and-answer text still helps readers who arrive with a specific fault in mind, so keep the questions on the page. If you add structured data at all, Google's LocalBusiness documentation is the page to read for a local firm, and Google says it does not guarantee that markup produces any feature in results.
What if a customer asks me to change or remove their review?
A review belongs to the reviewer, so you cannot edit it, and offering a refund or any other incentive to change or remove one is against Google's policy. You can reply publicly and put things right with the customer; whether to update the review is their choice, and you must not offer anything for it. If a review breaks the content policy, for example by being fake or abusive, flag it to Google instead.
Further reads
- AI Receptionist for Appliance Repair: Capture Model, Serial and Fault Code — Capture model, serial and fault code on the first call, ready for the fact sheet.
- Seven AI Tools for Appliance Repair Companies and What Each Costs — Seven AI tools an appliance firm can use, with costs.
- Appliance Repair Software Compared: Scheduling, Parts, Warranty and AI — Software that records jobs, parts and warranty, which feeds your page counts.
- How to Get More Google Reviews With Automated Review Requests — Automate the review request so it goes to every completed job.
- Phone Repair Shop Marketing: Local Search and Trade-In Offers With AI — Build repair pages from your own job data, ask every customer for a Google review after collection, and word trade-in offers that keep your margin.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Google Search Central spam policies (scaled content abuse and doorway abuse, updated August 2026), Google's guidance on helpful content (updated October 2026), the Search Central documentation changelog (FAQ rich result retired 7 May 2026), Google's LocalBusiness structured data documentation (updated September 2026), Google Maps review policy and Business Profile review tips, and Twilio's SMS encoding documentation. Job counts, prices and review rates in the examples are illustrative.