Content & Answer Pages · 8 min read · September 26, 2026 · Hafsa Tariq, gaash.ai
Fittings, setups and buying guides: a specialist store's advice in writing
An answer can say that your store fits shoes by appointment, or that someone on staff sets up guitars, only where a page says so. So write the advice down: a page for each fitting, sizing or setup service and whether it needs booking, staff by specialty with their consent, dated buying guides by your own people, and what you do after the sale.
Advice questions a shopper asks before buying
Some shopping questions ask for judgment rather than a product: "where can i get a bike fit near me", "running store that watches you run before suggesting shoes", "who does guitar setups in [city]", "bookstore with staff picks for a book club", "toy store that helps choose a gift for a [n]-year-old". Each one asks for someone's time or opinion, and behind each is a price, a wait and a rule about booking.
With web search on, an AI assistant reads a few pages before it replies. A fitting service that lives in one line of the About page, or only in the owner's head, gives an answer nothing to repeat about who does it, how long it takes or whether to book. Written down as its own answer page, the same service gives an answer something to repeat: who does it, how long it takes and whether to book.
A page for each fitting, sizing or setup service
Give each service a page that opens with what it is and who it is for, then says how long it takes, who does it, what it costs, whether it needs an appointment and what to bring. The table shows the shape for a few trades; every figure in it is yours to fill in.
| Service | What the page states | Booking |
|---|---|---|
| Bike fit | What is measured and adjusted, how long it takes ([n] minutes), the price ([price]) and whether a new bike includes it, and what to bring: shoes, pedals, the bike | By appointment, and how far ahead the calendar fills |
| Running shoe fitting | How it works (feet measured, pairs tried, a short run where you offer one), how long it takes, and whether it costs anything | Walk-in or booked, with the busiest times named |
| Instrument setup | What a setup covers (action, intonation, strings), the price ([price]), the turnaround ([n] days), and whether you set up instruments bought elsewhere | Drop-off with a ticket, or by appointment |
| Assembly and delivery | What you assemble (furniture, large toys, bikes), the price ([price]), the delivery area, and how a time slot is set | Chosen at checkout or by phone |
| Choosing help | Staff picks, gift advice by age or by reader, a reading list on request, and whether a one-to-one session needs booking | Walk-in, or booked for a quiet hour |
Keep the terms in the page's own text. A booking widget can stay, but the assistants' crawler documentation says nothing about running scripts, so wording that only the widget draws may never be read. In JSON-LD, each service can be a Service with a serviceType, a provider pointing at the store's own node, and an Offer for the price, written exactly as the page writes it:
{
"@context": "https://schema.org",
"@type": "Service",
"name": "[the service's name, as on the page]",
"serviceType": "[bike fit]",
"description": "[what happens, how long it takes, who does it]",
"provider": { "@id": "https://www.example.com/#store" },
"offers": {
"@type": "Offer",
"price": "[price]",
"priceCurrency": "[currency code]"
}
}The markup repeats the page, figure for figure. If the page says the fit comes free with a new bike, the Offer says the same and invents no price of its own.
Staff by specialty, listed only with their consent
Some advice questions are about a person: who on staff knows touring bikes, who sets up left-handed guitars, who reads for teenagers. A staff page answers them. It lists only people who have agreed to be on it, by the name they choose (a first name is enough), with their specialty, the days they are usually in and the languages they speak, and an entry comes down the day its person leaves.
Qualifications go on the page the way the issuing body names them, with a link to where they can be checked if the body keeps a public record. In markup, a staff member is a Person with worksFor pointing at the store, a jobTitle, and knowsAbout for the specialty, which schema.org defines as a topic known about, "suggesting possible expertise but not implying it". A qualification is hasCredential with an EducationalOccupationalCredential, whose recognizedBy names the body that awards it. The same entry is the author profile for any guide that person writes.
If the store belongs to a trade association, say so as membership: the association's own name, a link to its member directory and your membership number beside it. In markup that is memberOf on the store's node, pointing at the association as an Organization, which is how schema.org defines memberOf. A membership is not a license, a certification or a promise about the work, and the page does not present it as one.
Buying guides written by your own staff, dated and signed
A guide article is where a store's judgment can be written at length: how to choose a first road bike, what to check on a used acoustic guitar, which board games suit two players. Write it from what your staff know and have handled, sign it with the author's name (with their consent), put the date it was written and the date it last changed at the top, and say which of the options you sell.
State recommendations as opinion, and as whose: "[author]'s pick for [use], and why" rather than "the best [category]". A guide that recommends products the store sells says so plainly. Never write that one brand is better than another as a fact; write which suits which use, in whose view, and what would change the answer.
Google's guide to generative AI search lists a unique point of view among the attributes of helpful content, and gives a first-hand review based on personal experience as its example, set against a summary of what is available elsewhere. A guide your staff write from their own handling of the goods is that kind of page. Keep its date honest: Google's people-first content guidance, where its E-E-A-T questions come from, counts changing a page's date to make it seem fresh, when the content has not substantially changed, among its warning signs.
Mark the guide up as an Article with its headline, an image, datePublished, dateModified and an author with a url, the properties Google's article documentation lists. The author's url can be that person's entry on the staff page.
After the sale: servicing, repairs and trade-ins
What a store does after the sale is advice a shopper can ask about before buying: "bike shop that services e-bikes it didn't sell", "where to get a guitar re-fretted in [city]", "trade in old skis toward new ones". Put the after-sale work on a page of its own, with every price the store's own:
- The service menu: each job, its price ([price], or from [price]), and the turnaround ([n] days, longer when parts are ordered in).
- Whether you work on items bought elsewhere, and which makes or kinds you do not take.
- Trade-ins: what you accept, how it is valued, and whether it becomes store credit or money back, as your terms say.
- Warranty handling: what you do in the store, what goes back to the maker, and how long each takes.
Repair, warranty and trade-in terms touch consumer rules that differ between countries, states and provinces. The page states your terms, and your counsel checks them against the rules where you trade.
Putting the advice on the monthly panel
Written advice can be checked like everything else on the site. Add a line or two for your services to the store's monthly panel, such as "[service] in [city]" and "[repair] done this week near me", and record whether the answer named your store for the service and whether it had the booking rule and the price right.
The monthly reading for one store shows the panel and the columns, and the guide for retail stores places this work among the rest. The shape of a passage an answer can lift whole, a question in the heading and the answer in its first sentence, is in the article on writing to be cited.
Common questions
Should we publish prices for fittings and repairs that vary by job?
Yes, as the store's own range: "from [price]", with what moves the price up (parts, a second visit, an older model) and a line saying that a quote comes before any work starts. A range gives an answer one true thing to say about cost. With no price at all, a shopper asking what a fitting costs gets nothing from your page.
Can we name staff who might leave?
Only with their consent, and only while they work with you. Take an entry down the day someone leaves, and change any page that sends shoppers to them. Guides they wrote can keep their byline if they agree; if not, sign the guide with the store's name and the date it was last reviewed.
Our buying guide recommends products we sell. Is that a problem?
Not if the guide says so. State that you sell the products you recommend, write the picks as a named person's opinion with the reasons, and say what would suit a shopper you cannot serve, such as a size you do not stock. What a reader, or an answer, repeats from it is then honest in both directions.
Do we need a buying guide for every category?
No. Start with the questions staff answer at the counter every week, one guide for each main category, and date each one. A guide that is kept current is worth more than several that are not. Add the rest as the questions come, and retire a guide, with a note, when you stop selling what it covers.
Sources
This article quotes no statistics. What schema.org's types and properties mean is from schema.org's own pages, and what Google says about helpful content, dates and article markup is from its own pages, linked where used.
Sources: schema.org, Service · schema.org, Person · schema.org, memberOf · Google, article structured data · Google Search Central, optimizing for generative AI search · Google Search Central, creating helpful, reliable, people-first content
Read on