Technical SEO Audit for Tire Shops

You Are Auditing Two Sites That Share One Domain

A technical audit here has to cover a catalog and a garage at the same time, and the two halves fail in completely different ways. The catalog half holds thousands of SKUs, fitment tables that map each of them to dozens of vehicles, stock levels that change hourly and prices that move whenever a manufacturer runs a rebate. The garage half holds six service pages, a booking calendar, a phone number and a set of hours. One of those halves is e-commerce. The other is a local service business with four bays and a lift. No other local trade in this corpus carries that combination. A mechanic's entire URL set fits on one screen. A detailer's site is a portfolio. A tire shop is running retail infrastructure — faceted navigation, product feeds, inventory states, structured pricing — inside a building that closes at six. Which means the audit checklist a local agency brings to a service business will pass a tire shop site that is quietly hemorrhaging crawl budget, and the checklist an e-commerce agency brings will optimize a catalog that has no checkout at the end of it. Tire shop SEO needs both audits run at once, with the findings reconciled against each other, because the fixes for one half routinely damage the other.

Faceted Navigation Is Where the Crawl Budget Dies

Brand, season, load range, speed rating, run-flat, mileage warranty, price band, diameter. Eight filters with a handful of values each, combinable in any order, produce a crawlable URL space in the hundreds of thousands. Add a sort parameter and a pagination parameter and it is effectively infinite. Googlebot will happily spend weeks in there, and while it does, the pages that actually earn money — the alignment page, the location page, the fitment landing pages that match real searches — go recrawled once a quarter. The audit has to make a decision, not a recommendation, on every facet: indexable, crawlable-but-noindexed, or blocked outright. A useful default is that a single facet with genuine search demand behind it stays indexable — a size, a vehicle, a brand — while any combination of two or more collapses to noindex with a canonical pointing at the single-facet parent, and sort and pagination parameters are handled in robots.txt and the parameter rules rather than being left to chance. Every one of those calls needs to be written down with the reasoning attached, because the next developer who touches the filter component will otherwise undo it in an afternoon. The second half of the same problem is reachability. The same Michelin Defender in a 235/65R17 can be reached by size, by vehicle, by brand, by season and by a promotional collection. Five paths, five URLs, one tire. Without a canonical policy decided in advance, the shop is publishing five duplicates of its own inventory and asking a crawler to pick a winner.

Thin Size Pages Look Like Coverage and Behave Like Debt

The tempting move is to generate a page for every size the distributor lists. Two thousand tire size pages, each with a fitment table, a grid of products and a paragraph of templated text with the numbers swapped in. It looks like an enormous content asset. It is a duplication defect with a sitemap. The audit needs to sort those pages into three piles. The first pile has real search demand and real inventory behind it — the sizes this shop actually stocks and actually sells, which in most markets is a few dozen, not two thousand. Those deserve genuinely written pages: which vehicles wear this size, what a set costs installed on those vehicles, what the shop has on the shelf right now, and what the install involves. The second pile has demand but no stock, and those pages are honest only if they say so and offer an order window. The third pile has neither, and the correct treatment is to not publish it at all. The measurable symptom of getting this wrong is the ratio of indexed pages to pages that have ever received an organic click. On an unaudited tire catalog that number is routinely worse than ten to one. Trimming it is not a loss of coverage; it is the removal of a large body of near-identical text that was diluting the pages the shop can actually win. The same applies to model pages that differ only in the tread pattern name. No other discipline inside tire shop SEO produces a bigger single-day gain than deleting two thousand pages nobody was ever going to read.

Product Schema and Service Schema Are Both Correct, on Different Pages

This trips up almost every build. A tire is a Product: it has a brand, a model, a GTIN in many cases, an offer with a price and an availability state. An alignment is a Service: it has a provider, an area served, a price range and no inventory at all. A tire shop publishes both, and the audit's job is to draw the boundary and enforce it. On a product page the markup carries Product with an Offer, a real price, and an availability value that reflects the feed rather than an optimistic default of InStock. Marking an out-of-stock tire as available is the fastest way to earn a manufacturer feed penalty and a customer who drives across town for nothing. On a service page the markup carries Service, with the alignment price range stated honestly at $100 to $200 for four wheels and $50 to $100 for two, and the ADAS recalibration surcharge described rather than hidden. On a location page it carries LocalBusiness with the bay capabilities. Three vocabularies, three page types, no overlap. The out-the-door total deserves its own note. The installed price is the number the customer actually compares, and it is not the number in the product feed. Where a shop publishes an installed price, the offer markup should reflect what the customer will pay, not the naked tire price that will look like a bait-and-switch when the invoice arrives.

The Feed Is a Performance Liability Before It Is an SEO One

Price and stock arrive from a distributor, usually over an API, usually after first paint. A grid of forty tires waits on that call, the placeholders resize when it lands, and the layout shift score goes with it. Meanwhile the same call is being made server-side on every crawl, so the crawler's experience of the site is measured in seconds per page rather than in hundreds of milliseconds, and a shop that would pass Core Web Vitals with a brochure site fails them because it is doing retail work on a retail budget of nothing. The audit's findings here are mundane and load-bearing: cache the feed on the shop's own side with a sane time-to-live rather than proxying it live, render price and stock server-side into the initial HTML, reserve the layout space before the numbers arrive, and paginate the result grid so a size with two hundred matches does not ship two hundred product images to a phone on LTE. None of that is exotic. It is simply absent from the toolkit most local agencies carry, which is why so many tire shop sites are either a fast brochure with no catalog or a slow catalog nobody books on.

What the Audit Hands Back

A crawl map showing where the budget is actually being spent, with the facet combinations that are eating it named individually. A canonical and indexation policy written as rules a developer can implement rather than as advice. The three-pile sort of the tire size pages, with a publish, rewrite or remove decision against each. A schema boundary document. A feed-handling specification. A redirect map for anything being removed, because the wrong way to delete two thousand thin pages is to let them 404 all at once. And one number to watch afterward, which is not traffic. Traffic on a trimmed catalog often goes sideways for a quarter. What should move is the share of organic sessions that reach a page carrying an installed price and a booking path, because that is the only traffic that pays for anything.

Related Reading

The editorial half of this problem — deciding which sizes, vehicles and questions genuinely deserve a written page — is worked out in content strategy for tire shops, and the local half, where a shop with a slow-leak customer three miles away has to be findable in the map pack, is covered in local SEO and Google Maps. The closest technical parallel outside this vertical is SEO for boutiques, which runs a real online store: same faceted-nav sprawl, same feed, same duplication traps. The resolution is opposite, though. A boutique's catalog page is the end of the journey and the transaction happens there. A tire shop's catalog page cannot transact at all — it exists to hand a person to a bay calendar — which is why an audit that optimizes it purely for retail metrics will make the shop worse.