Schema & GEO Tactics
Getting found and cited by ChatGPT, Google AI Overviews, Gemini, Perplexity, and Claude — one entity, JSON-LD, crawler access, llms.txt, Bing/Brave coverage, and measurement
This page turns Wabu Web's AI Search Ranking Playbook v2 into specific tactics for Northwest Express Auto Care. Tags follow the playbook: [Established] means act with confidence, [Emerging] means act and measure, and [Speculative] means low priority. For this business, the biggest AI problem isn't missing content. It's conflicting identity. Google Maps, Bing, and Brave all send the "website" click to nwautocaretx.com. Bing, the main source ChatGPT reads from, shows a Yelp 2.5 / 15 rating next to the business. Brave, which Claude reads from, summarizes "third-generation, 45 years" and "Sunday 9–1." The order is: make every source agree on one business, then let the engines in, then publish the facts only this shop has, as text.
What's Live Now (2026-10-03)
| Lever | Status | Playbook tag |
|---|---|---|
| Server-rendered content (no JS needed) | Yes. Divi renders page copy into the raw HTML. | [Established] |
| AI crawlers allowed in robots.txt | Implicitly (only /wp-admin/ disallowed); no explicit Allow lines (L1) | [Established] |
| XML sitemap | page-sitemap.xml dies with a PHP memory fatal after ~184 s; 0 of 87 pages listed (C3) | [Established] |
| Fast, light pages | TTFB ~820 ms; 2.9 MB average HTML (~2.1 MB inline CSS); mobile Lighthouse 16 (H4) | [Established]: slow pages get dropped on AI crawler timeouts |
| Business schema | AutoRepair present with address and phone; hours wrong and invalid ("Sunday CLOSE", en-dash); no geo, sameAs, priceRange, areaServed; Article + Person "albertgalopastor1987" on 86 pages (H3) | [Emerging]: hygiene, not the citation lever |
| Service / Offer / FAQPage schema | None | [Emerging] |
| Answer-first passages | Long pages (~1,000–1,500 words), but few question headings with direct answers; prices only on /coupons/ (orphan) (M4) | [Established] |
| One business identity | Four name forms, four hour sets, two websites, a phone typo on Nextdoor, three founding stories (C2, H6) | [Established] |
| On-topic site | ~25 duplicate/legacy pages + Hello World indexable (H1) | [Established]: topical focus |
| Third-party presence | GBP 4.5 / 268; Yelp 2.5 / 15; BBB, CARFAX, Nextdoor, YP, MapQuest, D&B, Chamber, BestProsInTown exist; no YouTube, no Reddit | [Established] |
| Search Console / Bing Webmaster Tools | No Wabu access; property verified by an unknown account (C4) | [Established] |
| llms.txt | 404 | [Speculative]: do last (L1) |
One Entity Everywhere
Copy this block word for word onto the GBP description, Facebook, Yelp, Bing Places, Apple Business Connect, Nextdoor, YellowPages, BBB, and the About page intro (H6). When the same facts appear the same way everywhere, Maps and AI engines can reconcile the business without guessing. [Established] The items in [brackets] must be confirmed by the client before anything is published (open questions 4–6).
Pick one name form and never alternate. The playbook calls name fragmentation one of the most common reasons an entity isn't recognized. Today the site title on default pages says "NW Express Auto Care" (WordPress site name), the logo says "NW Auto Care", the GBP says "Northwest Express Care", and everything else says "Northwest Express Auto Care". Change the WordPress site name to match too.
JSON-LD: AutoRepair Node Fix (H3)
Set this in Rank Math → Titles & Meta → Local SEO (hours, social profiles, price range, geo) so it's generated sitewide. Also turn off the Article + Person author schema on pages (Rank Math → Titles & Meta → Pages → Schema type: None or WebPage). The sameAs list uses only profiles found live today. Add Google's own Maps URL, and confirm each profile is the right business before publishing.
Don't add aggregateRating from the Google reviews widget. Google treats self-serving review markup on a LocalBusiness as ineligible, and the rating differs by platform (Google 4.5, Yelp 2.5). Leave Sunday out of the hours entirely; that's how schema says "closed." priceRange "$$" is a placeholder; confirm it with the client. Remove the three "(confirm exact URL)" placeholders, or replace them with the live profile URLs, before pasting.
JSON-LD: Service + Offer (one per service page)
Example for the rebuilt /transmission-service/. Only include an Offer price the shop has confirmed. Here it carries the published Service Savings coupon, not an invented price.
JSON-LD: FAQPage (matching the on-page FAQ)
FAQ rich results no longer show for most sites, but the playbook says to keep the question-and-answer structure because it helps extraction. Mark up only questions that appear word for word on the page. [Emerging]
The Answer-Block Pattern
Every service page FAQ and every blog post section uses this shape. Engines score each passage separately, so each block has to make sense on its own when pulled out of the page. [Established]
Rules: question as the heading, then a 1–3 sentence answer that names the shop and Katy, then the detail. Use the exact terms people search ("transmission replacement", not only "drivetrain service"). Use named numbers only when the shop confirms them. No keyword stuffing.
robots.txt: AI Crawler mu-plugin (L1)
Wabu's standard pattern (first used on Greenlight Services, replicated on Texas Patio Pros): a small must-use plugin at wp-content/mu-plugins/ai-crawler-robots.php that appends explicit Allow: / lines for each AI crawler to whatever Rank Math already outputs. It's purely additive and can't be switched off from wp-admin. Search crawlers (OAI-SearchBot, Claude-SearchBot, PerplexityBot) are what get the shop into answers. Training crawlers (GPTBot, ClaudeBot, Google-Extended) are allowed by default too.
After deploying, verify live: curl -s https://nweautocare.com/robots.txt, then curl -s -o /dev/null -w "%{http_code}" -A "GPTBot" https://nweautocare.com/ (and the same for ClaudeBot and PerplexityBot). Each should return 200. That second check rules out a server-level bot block, which robots.txt can't show.
llms.txt Draft (L1)
The playbook rates llms.txt as [Speculative]: no major engine is known to read it. It's cheap and harmless, so add it at /llms.txt after everything else on this page, and only once the consolidation (H1) is done so it lists final URLs.
Reviews, Video, and Third-Party Presence
Google is strong (4.5 / 268, with owner replies), but Bing and therefore ChatGPT show Yelp 2.5 / 15 with three negative snippets. Claim Yelp, reply to every review there calmly, and ask satisfied customers to leave a Yelp or Facebook review as well as a Google one. On the site, filter the widget to 4–5 stars (H5). A 1-star "rip you off" review shouldn't be the AI-readable text on every page.
Two of the top 12 results for "auto repair katy" are Reddit threads (r/houston, r/Katy "car mechanic in katy"), and a Katy Facebook group post ranks for both "auto repair katy" and "oil change katy." The playbook calls these primary distribution. The honest play is a real account (owner or service manager, clearly identified) that answers car questions in r/Katy. No self-promotion and no fake recommendations, which get removed and backfire.
YouTube is the most-cited domain in AI Overviews, and the shop has no channel. Short, descriptive clips ("What a worn brake rotor looks like", "Texas state inspection: what we check") filmed in the bay can be embedded on the matching service page and posted to the GBP. Use click-to-load thumbnails so they don't slow the page (H4).
Find every "best auto repair in Katy" article or directory list that names competitors but leaves this shop out. The playbook says each one is actively suppressing the shop for that query cluster. Pitch the 2017 story, the TechNet warranty, and the review count for inclusion. Track the source URLs found in the quarterly citation check below.
Index Coverage Beyond Google
| Engine | Feeds | What we saw today | Action |
|---|---|---|---|
| AI Overviews, AI Mode, Gemini | Indexed; #1 for the brand. Maps entity named "Northwest Express Care" with the website set to nwautocaretx.com. No Search Console access. | C2, C3, C4 | |
| Bing | ChatGPT, Copilot | The brand search shows a local panel "Northwest Express Care" → nwautocaretx.com with Yelp 2.5 / 15; organic results: nwautocaretx.com #1, nweautocare.com #2, nwautocaretx.com/katy #3. A site: query returned no domain results. | Bing Webmaster Tools (import from GSC), IndexNow, claim Bing Places and set the website (C4, H6) |
| Brave | Claude | Indexed (home, About, Vehicles, Mobile Service, /auto-repair-in-katy-tx/, an old /smart URL). The AI summary repeats unverified facts ("third-generation", "45 years", "Sun 9–1", "$399 for four tires"). The map card links nwautocaretx.com. | Fix the sources Brave summarizes (directories, H6); consolidate old URLs (H1); Brave reads the open web, so there's no Brave console |
| Perplexity | Perplexity | Not checked today | Include it in the quarterly check below |
Measuring AI Visibility
- GA4 channel group (M5): add an "AI assistants" channel matching referrers chatgpt.com, chat.openai.com, perplexity.ai, gemini.google.com, copilot.microsoft.com, claude.ai. This needs one GA4 property the agency controls (today two unknown IDs fire: G-HF68X7Z5KG and G-F3ZB43T30G).
- Expect Direct traffic: the playbook notes that a large share of AI-driven visits arrive with no referrer. Watch call clicks and Shopmonkey bookings, not just referral sessions.
- Branded search: track "northwest express auto care" (110/mo today) and the Search Console impressions for brand queries as a trust indicator.
- Entity KPIs: Knowledge Panel / Maps entity correct (name, website), zero schema errors, NAP accuracy above 95% across the directories listed in H6.
Quarterly AI Citation Check
Run these 8 prompts in ChatGPT (search on), Perplexity, Google AI Mode, Gemini, and Claude, from a Katy location if possible. Log for each: whether the shop is named, its position in the answer, which website is linked (nweautocare.com or nwautocaretx.com), which sources are cited, and whether the facts are right. First run: right after C2 lands, to set the baseline. Then every quarter, starting January 2027.
| # | Prompt | What it tests |
|---|---|---|
| 1 | "What are the best auto repair shops in Katy, TX?" | Head-term recommendation, listicle sources |
| 2 | "Where can I get a transmission repaired in Katy, Texas?" | High-value service + the Facebook campaign topic |
| 3 | "How much does a transmission replacement cost near Katy TX?" | Whether the cost page gets cited |
| 4 | "Good place for brake repair in Katy that won't overcharge?" | Trust/sentiment (Yelp vs. Google reviews) |
| 5 | "Where can I get a Texas state inspection in Katy on a Saturday?" | Hours accuracy |
| 6 | "Tell me about Northwest Express Auto Care in Katy." | Entity facts: name, founding, website, hours, warranty |
| 7 | "Is Northwest Express Auto Care legit? What do reviews say?" | Which rating platform is quoted |
| 8 | "Auto repair shop in Katy TX with financing and a warranty" | Differentiators: TechNet warranty, financing |
The real value of this check is the source URLs each engine cites when it names a competitor and not this shop. Those URLs are the outreach list for "best of" inclusion and the directory fixes. Record results in the dated progress log on the Playbook Action Plan.