Rideout Law Group, Engagement Report v3.0

Headline Findings

Two stories, one 65-day window. Read these first.

Day-65 top-line numbers (June 2 data carried forward, live site data current)

1. Executive Summary

This is the day-65 checkpoint on Rideout Law Group's 90-day recovery engagement. The engagement was scoped April 27, 2026 in report v1.8 (Phase 1 close: 43 practice subpages, 25 statute-anchored blog posts, 3 legal pages, 17-template schema package, WCAG 2.2 AA audit). v2.0 measured day 35. This v3.0 measures day 65, with 26 days remaining until the 90-day KPI review on July 27.

The strategy is working; the execution isn't. Every leading indicator we could measure on June 2 pointed the right direction: DR held at 31, refdomains grew from 263 to 423, Top-3 keywords climbed from 48 to 55, the momentum cluster expanded from 5 to 35 keywords gaining 3+ positions. The strategy from v1.8 (statute-anchored blogs, cross-linking, schema, WCAG) is producing the expected leading-indicator lift. What has NOT happened is the Brad-side execution that would convert those leading indicators into traffic gains: the 3 declining pages have not been refreshed (65 days), the 404 URL has not been fixed (65 days), reCAPTCHA v3 swap has not shipped (65 days), and Google Search Console access still has not been granted. Recovery is bottlenecked on client-side execution.

The Ahrefs API blocker is a real problem for this checkpoint. Sometime between June 2 and July 1, the Ahrefs subscription that produced the April 27 and June 2 sweeps was downgraded, expired, or throttled. Every date-parameterized endpoint now returns HTTP 403 "Insufficient plan." Same API key. Same host. Same request headers. This is a subscription tier change we cannot reverse from our side; it needs Don and/or Kaizen accounting. Without Ahrefs and without GSC access from Brad, we are effectively flying blind on rank and traffic dimensions until one or both is restored. Recommend restoring the Ahrefs plan tier before the July 27 KPI review; the diagnostic value at day 90 is very high.

Live site data is fresh, reproducible, and mostly bad news. All Section 8 (Live Site Health) findings can be independently verified against rideoutlaw.com right now. The 3 legacy decliners are still on their 2024 dateModified. The federal-crimes 404 is still 404 (65 straight days). A new 404 hiccup surfaced on /contact-us/ (homepage uses /contact/, but historical inbound links to /contact-us/ break). accessibility@rideoutlaw.com still leaks on all 3 legal pages. reCAPTCHA is still v2. LinkedIn URL was fixed (1 shipped item in 65 days). Blog schema integrity held on the 5 spot-checked Phase 1 posts.

What Jen and Don get in v3.0. The updated day-65 recovery scorecard against 90-day KPIs (Section 2). What improved (Section 3). What regressed or didn't move (Section 4). The SEO trajectory (Section 5, June 2 numbers, no fresh Ahrefs). GEO status (Section 6). Phase 1 indexing snapshot (Section 7). The full live-site health audit including the 2 live 404s (Section 8). Re-evaluated Phase 2 recommendations (Section 9). The updated prioritized punch list (Section 10). What Brad still owes us and hasn't delivered (Section 11). Days 66-90 next steps (Section 12). Caveats and API blocker context (Section 13).

2. Recovery Scorecard - Baseline / Day-35 / Day-65 / 90-Day Target

The v1.8 report committed six measurable KPIs across a 90-day window. We are at day 65 (72% of the window elapsed). The "expected pace" column shows where each metric would be on a linear glide path from baseline to target. The "day-65 status" is scored conservatively because the day-65 Ahrefs numbers are the June 2 snapshot carried forward (see Section 13).

Scoring summary. Of 9 measurable metrics, 1 is ahead of pace (refdomains, flagged for unverified drift since June 2), 3 are behind pace (DR, Top-3 keywords, AIO), and 5 are off track (organic keywords, traffic, Phase 1 URL live rate, decliner refresh, Brad unblocks). The 4 leading-indicator metrics were on the right trajectory as of June 2. The 5 execution metrics have not moved.

The honest read. If Ahrefs data does refresh with fresh July 1 numbers before the 90-day review, and if we assume the June 2 trend held, the leading indicators should be pushing further ahead. Refdomains and Top-3 keywords have real chance to hit or exceed the 90-day target. DR at 32 is achievable if the momentum cluster continues expanding. AIO 50% is a stretch. Organic keywords 1,200 and traffic 2,400 are almost certainly not going to be hit at this pace without the legacy refresh executing this month. The 3-decliner refresh remains the single highest-leverage unlock for the traffic line.

3. What Improved Since Last Audit (June 2 to July 1)

Everything measurable that pointed in the right direction across the 30-day window between v2.0 and v3.0.

The single confirmed dev-side win in 30 days: LinkedIn URL was fixed. That is a real ship. Everything else in this table is either "held steady" or "not measurable due to Ahrefs blocker." No new regressions. The Phase 1 build is stable.

4. What Regressed or Did Not Move

The honest counterweight to Section 3. Every item that should have moved and did not.

New this window (day 35 to day 65): Ahrefs API access lost. /contact-us/ 404 discovered (see Section 8). No offsetting Brad-side delivery beyond the LinkedIn URL fix.

The pattern is unambiguous. Brad's team can execute on discrete developer tickets (LinkedIn URL was a code-level fix). What is not happening is any of the higher-effort items: content refresh, alias purge, plan-tier access grants, reCAPTCHA v3 migration. The 3-decliner refresh alone would recover an estimated 100-200 monthly visits within 4-6 weeks of redeploy; that's the single largest unrealized value in the engagement right now.

5. SEO Performance: 12-Month Trajectory + Day-65

5.1 Extended domain trajectory

The last measured window (April 27 to June 2) told a clean directional story: DR held at 31, refdomains climbed 263 -> 322 -> 423, Top-3 keywords climbed 48 -> 57 -> 55, but total keywords and organic traffic continued to compress on the tail. That compression was concentrated in the 3 legacy decliners and a broader long-tail contraction. On July 1 we cannot independently verify whether that trajectory held or reversed. The live site has been stable but static (no new content published in 30 days), so absent a major algorithmic change the June 2 pattern is the best available proxy for July 1 state.

5.2 3-Decliner status (Ahrefs data from June 2, live-site refresh check from July 1)

Live-site verification on July 1: All three URLs still return HTTP 200. /what-should-women-wear-to-court/ still carries dateModified: 2024-06-03T23:26:00+00:00 in Yoast schema. The other two still have no dateModified in the HTML at all. Content hashes were captured on July 1 and can be diffed against the April 27 snapshots when Brad grants refresh authority.

5.3 Anchor profile (June 2 data, still healthy)

Profile remained healthy on June 2 with branded plus naked URL combined at 68.6% and zero exact-match commercial anchors. Cannot re-verify July 1 without Ahrefs access, but the anchor mix rarely swings materially in 30 days on a mature site with no new promotional link-building underway.

6. GEO / AI Search Visibility

6.1 SERP feature distribution (June 2 vs April 27 trend; July 1 blocked)

AIO on 44% of top-100 keywords (June 2). The strategic call is unchanged from v2.0: continue building AIO-friendly answer blocks on ranked pages. Absent fresh data, the priority framing holds.

6.2 GEO instrumentation status

• HubSpot AI Search Grader: still not run (v2.0 said "recommend running during next session"). Zero-cost, 15 minutes. Recommend Don approves running it before July 27.
• Otterly.AI: still unbudgeted. $29/mo. Recommend Don approves subscription budget line for ongoing GEO tracking.
• Manual prompt log: still not started. Recommend Dr. Strange starts logging manually on top 10 high-intent queries this week for baseline (independent of Otterly).

Because Ahrefs is blocked and GSC access is still pending, LLM-citation instrumentation is now the primary way we can measure day-60/day-90 impact. Even the free HubSpot pass would give a v3.0 baseline before the July 27 KPI review.

7. Phase 1 URL Indexing Status

7.1 Live HTTP status across 71 URLs (July 1)

7.2 Ahrefs indexing status (June 2 data carried forward)

The two Phase 1 URLs that had entered Ahrefs' ranking index as of June 2:

Both URLs still return HTTP 200 on July 1 with intact BlogPosting and FAQPage schema (spot-checked in Section 8). We cannot verify whether additional Phase 1 URLs have entered the Ahrefs index in the last 30 days because the API is blocked. Ahrefs typical latency on moderate-DR domains is 8-12 weeks, so day-65 (65 days post-deploy) is within the plausible ramp-up window. If we had GSC access, we would be able to see actual Google indexation, which is likely meaningfully higher than the Ahrefs count.

7.3 Interpretation and forecast

The Section 6 (v2.0) hypothesis was that we should see the Ahrefs indexing rate ramp to 30-50% by day 60 and 70-90% by day 90 with three specific accelerators (GSC access, 404 fix, internal-link injection to unindexed URLs). None of the three accelerators shipped in the 30 days between v2.0 and v3.0. Without them, and without fresh Ahrefs data to measure, we cannot confirm whether the natural discovery curve has produced additional indexed URLs at day 65. Best-effort forecast for day-90 (July 27): if the API is restored and the accelerators still don't ship, expect Ahrefs indexing rate 5-15% (natural discovery only). If GSC access lands and we execute internal-link injection this week, day-90 can reach 30-50% in Ahrefs.

8. Live Site Health Report (July 1)

Every finding below is from a fresh HTTP layer scan against rideoutlaw.com on July 1, 2026. All findings are independently reproducible. Raw dumps stored at /data/workspace/clients/rideout-law/live-audit-2026-07-01/.

8.1 Live 404 errors (2 total)

The /contact-us/ 404 is a new finding this window. The homepage navigation and internal links use /contact/, which resolves to HTTP 200 and serves the contact page correctly. But any legacy inbound link, cached search-result snippet, marketing collateral, or third-party directory listing that points at /contact-us/ now hits a dead page. This is a low-medium impact issue; the fix is a single WordPress redirect rule or .htaccess entry.

8.2 Content freshness on the 3 legacy decliners

Zero of the three declining pages have been touched since v1.8 flagged them 65 days ago. Refresh briefs sit in /data/workspace/clients/rideout-law/seo-optimized/ and can be deployed within 48 hours of Brad granting authority.

8.3 accessibility@rideoutlaw.com leakage on legal pages

The v1.8 recommendation was to consolidate to brad@rideoutlaw.com only. The accessibility@ alias is still referenced on all three legal pages, unchanged from June 2. This is a WP post-edit ticket for Brandy or Brad's admin; total effort is under 30 minutes.

8.4 Contact form security: reCAPTCHA version

Contact form loads reCAPTCHA v2 (unchanged from June 2). Evidence:

• Loader script: https://www.google.com/recaptcha/api.js?hl=en&ver=6.9.4#038;render=explicit
• Sitekey: 6Le0DDEsAAAAALLLUYDQepAGxDE-EU09YQeKMjD_ - starts with 6L, confirming v2
• No grecaptcha.execute() call anywhere in the contact page HTML (v3 requires this)
• No hidden score-based challenge; still using the "I'm not a robot" checkbox

BB-DEV-TODOS item for reCAPTCHA v3 swap has not been executed in 65 days.

8.5 LinkedIn URL (BB-DEV-TODO) - FIXED

Confirmed on the homepage and contact page:

• Homepage: 3 references to linkedin.com/company/rideout-law-office/, 0 to /admin/
• Contact page: 2 references to /company/rideout-law-office/, 0 to /admin/

This is the one confirmed BB-DEV-TODO ship in 65 days.

8.6 Blog schema integrity (5 of 25 spot-checked)

All 5 spot-checked Phase 1 blog posts retain both required JSON-LD blocks. Phase 1 schema is holding. No regressions.

8.7 New content published since June 2

• GET /wp-json/wp/v2/posts?after=2026-06-02T00:00:00&per_page=100 -> 0 posts
• GET /wp-json/wp/v2/pages?after=2026-06-02T00:00:00&per_page=100 -> 0 pages
• Sitemap index lastmod on post-sitemap.xml: 2026-04-27T12:41:24+00:00 (Phase 1 close date)
• Sitemap index lastmod on page-sitemap.xml: 2026-04-26T13:00:38+00:00

Zero new content in 30 days. Site has been effectively static since Phase 1 close. This is the direct cause of the flat SEO trajectory: search engines have nothing new to crawl, which means no new keyword targets are being introduced.

8.8 Sitemap URL counts (unchanged)

8.9 Random 20-URL sample HTTP audit

Sequential HTTP GET against 20 randomly-sampled Phase 1 URLs (seed 65) returned 20 of 20 HTTP 200. Sample saved to /data/workspace/clients/rideout-law/live-audit-2026-07-01/phase1-sample20.json. No new breakage detected outside the two 404s already flagged.

9. Updated Phase 2 Recommendations

The v1.8 report committed 5 strategic plays. v2.0 added a 6th sub-track (indexing acceleration). v3.0 adds a 7th (Ahrefs plan restoration) and re-evaluates all 7 against day-65 evidence.

10. Actionable Items - Prioritized Punch List

Mirror of the June 3 summary structure with July 1 status. Reordered by urgency for the days-66-90 window.

Priority 1 - Ship this week (Kaizen-controlled, no Brad approval needed)

1. Add 301 redirect from /contact-us/ to /contact/. WordPress Yoast redirect module or .htaccess entry. Fixes the newly-discovered 404. Estimated 15 minutes via Brandy WP admin. Not started
2. Start the AIO answer-block rollout on the top 20 highest-traffic pages. 60-90 word Q-and-A intro block plus FAQPage schema. Kaizen can execute unilaterally via Brandy admin. Estimated 2-3 days. Not started
3. Internal-link injection from high-momentum legacy pages to unindexed Phase 1 URLs. The Rec 6 sub-track. Kaizen can execute via Brandy. Estimated 1 day for full pattern. Not started
4. Run HubSpot AI Search Grader baseline. Zero-cost, 15 minutes. Establishes v3.0 GEO baseline before July 27. Not started
5. Start manual LLM prompt log on top 10 high-intent queries. Log responses in workspace; independent of Otterly budget question. Not started
6. Draft the Rideout Page Spec from the June 2 momentum data. Even without fresh July 1 numbers, the June 2 momentum cluster gives enough pattern to document. Not started

Priority 2 - Ship in the next 2-4 weeks (needs Brad unblock)

7. Refresh the 3 known legacy decliners (women-wear-court, squatters-rights, felons-passport). Blocked on Brad refresh authority. Refresh briefs sit in workspace ready to deploy on approval. Blocked 65 days
8. Fix the /criminal-defense/federal-crimes-defense-lawyer-scottsdale/ 404. Blocked on Brad dev team. Either deploy the page or remove from Phase 1 manifest. Blocked 65 days
9. Purge accessibility@rideoutlaw.com from Privacy, Terms, and Accessibility pages. Consolidate to brad@. Can execute via Brandy WP admin if Don approves the copy edit unilaterally; recommend Don confirms. Blocked pending Don sign-off on copy edit
10. reCAPTCHA v3 migration. Blocked on Brad dev team. BB-DEV-TODO item pending 65 days. Blocked 65 days

Priority 3 - Brad unblocks needed by July 27 KPI review

11. Restore Ahrefs API plan tier. Escalate to Kaizen accounting or Brad, whichever is the billing owner. Blocks all rank/traffic measurement.
12. GSC access from Brad. 65 days pending. Blocks true Google indexation view.
13. GA4 read-only access from Brad. 65 days pending. Blocks lead/conversion measurement.
14. GBP owner-verify both offices. 65 days pending. Blocks local pack visibility gains.
15. 3 attorney bios (Eckhardt, Keist-Gilbert, Hibbler). 65 days pending. Blocks 3 of 17 Person/Attorney schemas.
16. 5-10 first-party client testimonials with named clients. Blocks aggregateRating schema and SERP star-rating eligibility.
17. 8-12 anonymized case results. Case-results page drafted and awaiting real data.
18. High-resolution photos (Brad headshot, team, both offices). Blocks 3 SEO-optimized location/bio deploys.
19. Arizona counsel review of Privacy Policy and Terms of Service. Legal review only; accessibility@ purge is separate.
20. Confirmation of current attorney roster for WPML Spanish and legacy English cleanup.

11. What We STILL Need from Brad

v1.8 listed 10 unblocks. v2.0 measured 0 fully delivered at day 35 (1 partial, LinkedIn URL). v3.0 measures the same list at day 65.

12. Recommended Next Steps for Days 66-90

Windowed against the July 27 KPI review 26 days out. Split into what Kaizen can do unilaterally, what needs Don's sign-off, and what needs Brad-side execution.

12.1 Week 1 (July 2-8) - Kaizen-controlled sprint

1. Add 301 redirect from /contact-us/ to /contact/ via Brandy WP admin. 15 minutes.
2. Run HubSpot AI Search Grader baseline. 15 minutes. Establish v3.0 GEO reading before July 27.
3. Start manual LLM prompt log on top 10 high-intent queries (5 criminal defense, 3 DUI, 2 family law). Log format: query + full LLM response + citation footprint. Daily.
4. Draft the Rideout Page Spec from the June 2 momentum data. Document the 3-5 templates producing the wins (averhealth locations, women-wear-court, dangerous-offense, aggravated-dui, mvd-locations). Publish to workspace.
5. Begin the AIO answer-block rollout on the top 20 highest-traffic Rideout pages. Priority: pages already ranking top-20 for their target keyword. 60-90 word Q-and-A intro; FAQPage schema markup.
6. Begin internal-link injection from high-momentum legacy pages to the 69 still-unindexed Phase 1 URLs. Pattern: 2-3 contextual links from each momentum-cluster page pointing at the closest-topic Phase 1 URL.

12.2 Week 2 (July 9-15) - Escalation and instrumentation

7. Don escalates Ahrefs plan tier restoration with Kaizen accounting. Prerequisite for a credible day-90 report.
8. Don escalates GSC access, GA4 access, GBP verification, and 3-decliner refresh authority in the next Brad call as a single-page list.
9. Don approves the accessibility@ purge as a copy edit (Kaizen executes via Brandy admin) or Kaizen defers pending Arizona counsel review with the rest of Privacy/Terms.
10. Continue AIO rollout (weeks 1-3 total for top 20 pages).
11. Continue internal-link injection.

12.3 Week 3 (July 16-22) - Recovery execution

12. If Brad refresh authority arrived: refresh the 3 legacy decliners against the Rideout Page Spec. Redeploy in the second half of week 3.
13. If Ahrefs plan restored: run the day-80 mini-sweep (Sections A through I) to establish a fresh trajectory anchor before the July 27 review.
14. If GSC access arrived: pull the true Phase 1 indexing count as of Brad's data window.
15. Continue AIO rollout finish-up. Complete manual LLM prompt log for its second week of data.

12.4 Week 4 (July 23-27) - 90-day report

16. Run the full day-90 Ahrefs deep sweep (assuming plan is restored). Compare against April 27 baseline and June 2 day-35.
17. Compile v3.5 or v4.0 engagement report. Full 90-day KPI scorecard. Real recovery narrative or honest "measurement blocked" narrative depending on what unblocks by then.
18. Recommend Phase 3 scope to Don and Brad. Options depend heavily on what unblocked; most likely Phase 3 anchors on the PI vertical + full content pipeline restart + link acquisition push.

13. Data Quality Caveats and Limitations

• Ahrefs API v3 blocked at plan-tier level. Every date-parameterized endpoint returned HTTP 403 {"error":"Insufficient plan"} during the July 1 sweep. Endpoints tested: domain-rating, backlinks-stats, metrics, pages-by-traffic, organic-keywords, refdomains, subscription-info/limits-and-usage. Same API key, host, and headers that worked on June 2 now fail identically. Diagnosis: Ahrefs subscription tier changed since June 2 (downgrade, expiration, or throttle). Impact: no fresh SEO trajectory data for July 1. All Section 5 numbers are the June 2 snapshot carried forward with clear labeling.
• Cloudflare rate-limit on initial parallel scan. The initial 15-thread parallel HTTP scan against 71 Phase 1 URLs triggered rate limits at the WP host and returned 000 codes on 67 of 71 URLs. Sequential scan with 2-second delay confirmed 20 of 20 sampled URLs return HTTP 200. Full 71-URL parallel scan aborted; Phase 1 HTTP status carried forward from June 2 baseline (70 of 71) plus confirmed 20-URL sample.
• June 2 Ahrefs numbers may have drifted. Refdomains had grown +160 between April 27 and June 2 (263 -> 423). If that trajectory reversed after June 2, the day-65 refdomain number could be lower than 423. Without API access we cannot verify.
• Phase 1 Ahrefs indexing rate is a lower bound. Ahrefs typically takes 8-12 weeks to fully discover, crawl, and start attributing ranking keywords to new content on moderate-DR domains. Day-65 puts us at the front edge of the natural discovery window. Google indexation via GSC would show a meaningfully higher number, but GSC access is still pending.
• WP REST API access via Brandy account. Post/page publish-date queries confirmed against rideoutlaw.com/wp-json/wp/v2/. Zero new posts and zero new pages since 2026-06-02. Sitemap-index lastmod dates are consistent.
• Live-site content freshness checks are HTML-source based. dateModified was searched in the raw HTML for Yoast schema and Open Graph article:modified_time. Absence of a dateModified attribute does not prove the file was not edited server-side; it does prove that no schema signal is being sent to search engines about a refresh. Content-hash SHA-256 of each of the 3 legacy decliners was captured on July 1 and can be diffed against April 27 snapshots when time permits.
• BB-DEV-TODO execution is a spot-check, not a full sweep. LinkedIn URL was verified fixed. reCAPTCHA was verified still v2. H1 consolidation, aria-labels, and GBP schema completeness from BB-DEV-TODOS were not re-checked this window; those findings carry the June 2 assessment forward.
• SERP feature and momentum data is 30 days stale. All Section 6 (GEO/AI) and Section 5.1 (trajectory) numbers are the June 2 pull. Cannot re-verify July 1 without Ahrefs. AIO trend direction was +2 points across the prior window; assumed direction still positive for the 30-day gap absent contradicting data.