The short version of your AnswerShare test run on www.texasfirstrentals.com: one rewrite rule your team reviews and deploys, about two weeks from kickoff to production, and a seven-day soak before handover. The schedule below shows how the weeks fit together; the Architecture tab shows what happens to a request once the rule is live. Nothing is deployed to texasfirstrentals.com yet, and nothing goes live until HOLT has approved the rule, the data processing agreement and the preview.
Status on 23 October 2026: not live. Shane Wall asked on 21 October 2026 to move forward with a test run, and the kickoff call is not yet booked. Weeks count from kickoff, and calendar dates are set on that call. [Kevin to confirm: kickoff date]
| Activity | Weeks from kickoff | |||
|---|---|---|---|---|
| Kickoff call, Week 0A technical call with Stephen Marston and your engineers. We agree the test window, the contacts and the access requests. | ||||
| Your review of the rule and the data processing agreement, Weeks 0 to 1Your engineers review the rule and the crawler list. Your counsel reviews the agreement. | ||||
| AI version build, Weeks 0 to 2Our work. We finish the AI versions of your English and Spanish pages while you review. | ||||
| Vercel preview and pre-launch tests, Weeks 1 to 2Your team opens the preview. We run the test matrix and share every result. | ||||
| Production enable on www, Week 2Your team deploys the rule in a deployment of its own, with Stephen and our engineer both online. | ||||
| 7-day soak, Weeks 2 to 3We check every minute. You can ask for a revert at any time. | ||||
| Handover call, Week 3, after day 7 of the soakWe walk your team through the dashboard and give access on this call. | ||||
Your detailed plan, the rule, the preview tests and the measurement plan are in the test run package. Your onboarding task page is here. The proposal is here.
AI assistants describe Texas First Rentals from what they can find. Your proposal records that Texas First Rentals is named in 13 of 15 saved answers and 3 of 5 discovery answers, and that fleet, delivery, service and trench-safety facts are scattered across pages. The AI version of each page organizes those facts, in plain text, with the live page they came from and the date we captured them.
Stephen Marston is already your point of contact for the technical setup, and Shane Wall owns the test run. We need three more names so each message reaches the right person.
Click flow: Your onboarding task page (open it here) > Your part now > Who runs the website > Who approves what we publish about Texas First Rentals: enter name and email > Mark this step done
You should see: the step marked Done with the approver's name shown. We confirm the exact labels on the call.
The kickoff call starts the schedule above. Stephen Marston and an engineer from HOLT join, with Kevin Myers and our engineer.
Click flow: Book the kickoff call > pick a date and time > Confirm
You should see: a confirmation page with the date, time and a calendar invitation in your inbox.
Your counsel reviews the draft agreement. AnswerShare never receives data about your visitors, and the agreement says so in writing.
Click flow: Data processing agreement page > AnswerShare-TFR-DPA-DRAFT.docx: download
You should see: the Word file AnswerShare-TFR-DPA-DRAFT.docx saved to your computer, marked as a draft.
The rule is one rewrite in your next.config.js. Your engineers review the text and the list of named AI crawlers, and remove any crawler you do not want served. Nothing is deployed until you merge it.
Click flow: The rule page > How it decides > Named AI crawlers: strike any name you do not want served
You should see: the list of named AI crawlers and the line "Rule version 0.1".
Five of your pages, three English and two Spanish, shown beside their AI versions. Each fact carries the address of the live page it came from and the date we captured it.
Click flow: Side-by-side pages > Home (English) > Facts checked: read the table
You should see: a table of facts with the live page on one side, the AI version on the other, and a Source line with the page address and capture date.
We found Google Tag Manager on your site but could not see the GA4 property. Viewer access lets us read aggregate reports of AI-referred sessions, before and after launch. We never pull revenue, transactions, conversions, funnels or user-level data.
Click flow: analytics.google.com > the Texas First Rentals property > Admin > Property access management > + > Add users > aria@aryah.ai: Viewer
You should see: aria@aryah.ai in the list with the role Viewer.
We could not see a Search Console verification record. If the property is verified another way, add us as a Restricted user. If it is not set up, tell us and we plan without it.
Click flow: search.google.com/search-console > www.texasfirstrentals.com > Settings > Users and permissions > Add user > aria@aryah.ai: Restricted
You should see: aria@aryah.ai in the Users and permissions list with the permission Restricted.
Your Vercel request counts are the only "before" count of AI-crawler visits. We want counts by user agent only, no IP addresses. If Vercel keeps no history on your plan, we report crawler visits from launch onward and say so. [Kevin to confirm: how far back HOLT's Vercel plan retains request logs]
Click flow: vercel.com > your team > the Texas First Rentals project > Logs > filter by user agent (GPTBot, ClaudeBot, PerplexityBot) > last 30 days: counts only. We confirm the exact menu names on the call.
You should see: a count of requests per AI-crawler user agent for the last 30 days, with no IP addresses.
Your team opens two previews from the same branch point. Preview A has the rule. Preview B is the same commit without it, as the control. We run the pre-launch test matrix against them and share every result. Vercel previews are often protected, so you choose how we reach them. [Kevin to confirm: whether HOLT runs our test script or gives a protection-bypass value on a call, never by email]
Click flow: vercel.com > your team > the Texas First Rentals project > Deployments > the preview built from the branch that carries the rule: Ready. We confirm the exact menu names on the call.
You should see: the preview deployment with the status Ready and a preview address you can open.
When your site deploys, one short step sends us the addresses of the pages that changed, signed with a secret we hand over on a call, never by email. We refresh the AI version of those pages within minutes. We never poll or crawl your site on a schedule to find changes. [Kevin to confirm: the link to the publish webhook guide, version 1.0 of 8 October 2026, and where HOLT's deploy step lives]
Click flow: your deploy pipeline > the step that runs after a production deploy > add the webhook step from the guide: enabled. We confirm the exact steps on the webhook test session.
You should see: the step in your deploy log, and a test delivery we confirm on the call.
Two views help us build the question set from your own data: pages with their keywords and monthly search volume, and keywords mapped to pages. Any tool's export works. This does not block the build. [Kevin to confirm: whether these exports were already requested]
Click flow: your SEO tool > Export > page planning CSV and keyword mapping CSV > share the folder with aria@aryah.ai: Viewer
You should see: both files in the shared folder, with the export date, tool and market in the file names or a note.
Our work, not yours. It needs nothing from your team beyond the answers above.
Your team merges and deploys the rule in a deployment of its own, in a slot when Stephen Marston and our engineer are both online. We repeat the core tests against www within the first hour. [Kevin to confirm: weekday and time of the production-enable slot]
Click flow: your Git host > the Texas First Rentals repository > the pull request with the rule > Merge: merged; then vercel.com > your team > the Texas First Rentals project > Deployments > Production: Ready. We confirm the exact menu names on the call.
You should see: a Production deployment with the status Ready, and our core tests passing on www.
To revert at any time:
Click flow: vercel.com > your team > the Texas First Rentals project > Deployments > the production deployment before the rule > Instant Rollback: confirm
You should see: the earlier deployment marked as Production, and the rule no longer active.
We check every minute that search crawlers and browsers still get your normal pages, that AI crawlers get the AI version, and that error rates and response times stay inside the agreed limits. Our AI-crawler traffic watch alerts us if AI-crawler traffic stops.
After day 7 of the soak we walk your team through the AnswerShare dashboard and give dashboard access on this call. Access is given only at the handover, after the soak. [Kevin to confirm: handover call date, and the named users who need dashboard accounts]
The FAQ review is a post-launch task, and nothing before production waits on it. Until you approve the FAQ, the AI version carries only FAQ content already published on your site, never the draft. The draft we sent on 18 October moves to this step.
| Item | Value |
|---|---|
| OwnerTexas First Rentals is a Texas equipment-rental business within HOLT Companies, according to its AnswerShare proposal. | HOLT Group. Shane Wall owns the test run; Stephen Marston is the technical contact. |
| DNSNot touched. The www record keeps pointing at Vercel. Read on 8 October 2026. | Network Solutions (ns95 and ns96.worldnic.com) |
| WebsiteServer-rendered, not a single-page app. Many pages are prerendered, which is why the rule sits in next.config.js and not in vercel.json. | Next.js App Router, hosted on Vercel |
| PagesSitemap read on 8 October 2026. | 497 page addresses: 377 equipment, 42 locations, 42 news and 36 other |
| LanguagesYour language routing is untouched. The rule runs after it, so it covers both. | English at / and Spanish under /es-US |
| How AnswerShare connectsOne rewrite rule in beforeFiles. No middleware, no code on any visitor's request, no credential in your project. | A rewrite rule in next.config.js, reviewed, merged and deployed by your team |
| EmailMail runs on a different part of your setup and is not touched. Read on 8 October 2026. | Proofpoint for mail routing, Microsoft 365 in the SPF record |
| Web analyticsWe could not see the GA4 property ID. See the Tasks tab. | Google Tag Manager detected |
| Search ConsoleNo verification record was visible. | Not detected |
| How content stays currentWebhook, not polling. Our page fetcher uses its own user agent, which the rule does not match, so a refresh always reads your normal page. | A signed publish notice from your deploy, with the addresses of changed pages |
| What you approve firstEach is a written approval with a named approver and a retained timestamp. | The rule version, the data processing agreement and the preview pages |
| Dashboard accessNever at kickoff or at production enable. | At the handover call, after the 7-day soak |
| Measure | Value |
|---|---|
| GEO scoreMedian of five engines. Measured 6 October 2026 23:07 UTC, comparison_scores row 0d5e398e-82ef-4d4f-a334-9ac99bf0f223. Grok 49, Perplexity 47, Claude 31, Gemini 50, OpenAI 55; Claude dropped as an outlier. | 49.5 |
| SEN (brand sentiment)Same row. Grok 65, Perplexity 0, Claude 5, Gemini 50, OpenAI 50. | 50 |
| RR (Relevance Ratio)Same row. Home page: 1,267 characters of content out of 2,299 visible. | 0.5511 |
| RTC (Retrieval Token Cost)Same row. Home page: 67,753 tokens, 0.052 seconds to last byte, 1,267 useful characters. | 2.7807 |
| Answer shareNo prompt set exists yet. We build it from your data and review it with you before the first run. Checked 21 October 2026. | Not yet measured |
| AI-crawler visitsWe have no view of your traffic until the rule is live. Your Vercel counts are the only before source. | Not yet measured |