Rideout Law Group SEO + GEO Audit

Executive summary

What changed since the last audit

This report and its crawl data are now the dated baseline of record for future full-site comparisons.

Errors, hiccups, and items to update

Technical and on-page evidence

Indexation and crawl control

• Pass: robots.txt is accessible and references sitemap_index.xml.
• Pass: preferred protocol and host variants ultimately resolve to https://rideoutlaw.com/.
• Fail: 4,488 tags, 418 categories, 3 author archives, test or utility pages, and thank-you pages are present in the sitemap.
• Fail: no sitemap page was marked noindex, so low-value archives are intentionally eligible for indexing.
• Warning: 4,520 URLs have no links from another crawled sitemap page. Most are taxonomy archives. Static-crawl limitations apply, but WordPress server-rendered links make the scale meaningful.

On-page templates

• Core pages have canonical tags, substantial copy, and concise meta descriptions.
• Primary practice pages omit a real H1. The source includes internal comments acknowledging the template problem.
• 743 titles exceed 60 characters. Many belong to archives and long-tail posts.
• 52 title values and 16 meta-description values are duplicated across multiple URLs.
• 252 URLs triggered image-alt review. Decorative lazy-load placeholders create false positives, so image-by-image confirmation is required before editing.

Performance and security observations

• Median HTML size was 364 KB. The 90th percentile was 381 KB.
• Median response time was 2,378 ms. The 90th percentile was 3,054 ms. These are server-side crawl proxies, not Core Web Vitals.
• The homepage returned a 490 KB HTML document. Repeated lazy-load and noscript markup contributes to page weight.
• The observed Content Security Policy only contained upgrade-insecure-requests. HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy were not observed on sampled pages.
• PageSpeed Insights returned HTTP 429. Lighthouse and field Core Web Vitals are [unavailable].

GEO and entity-readiness analysis

Rideout has enough topical content to become a strong source, but AI systems receive conflicting and incomplete entity facts. Fixing the graph should precede more publishing.

AI money-question probes

Live AI probes require browser access or provider credentials. Neither was available during this run. No answer, citation, or competitor result has been fabricated.

Entity repair specification

1. Define one Organization entity and one LegalService entity per staffed office, each with a stable @id.
2. Correct the canonical business URL and match every NAP field to the corresponding GBP and citation profile.
3. Add Person entities for each attorney with bar admissions, practice areas, employer, public professional profiles, and verifiable press relationships.
4. Connect service pages to the correct office and attorney entities using provider, areaServed, and stable IDs.
5. Add visible, concise Q&A blocks that answer the five money questions and apply FAQPage markup only where eligible.
6. Decide whether AI training crawlers should be allowed. Keep answer/search crawlers accessible if AI visibility is a goal.

Coverage of the 21-module system

Modules requiring private analytics, Ahrefs, live GBP interaction, review pagination, or AI-provider access are marked unavailable. Observable website and entity modules were completed against the live site.

Prioritized action plan

30-day sequence

1. Week 1: schema domain correction, location entity split, H1 repairs, public social-link repair, source-comment cleanup.
2. Week 2: taxonomy inventory. Preserve only useful hubs. Apply noindex and remove low-value archives from XML sitemaps.
3. Week 3: connect measurement platforms and produce the GSC page-two and high-impression, low-CTR list.
4. Week 4: update the first ten money pages, validate schema, rerun the crawl, and repeat the 15 GEO questions.

Scope, method, and limitations

Completed

• Full XML-sitemap crawl of 5,899 unique URLs.
• Status, title, description, canonical, robots, H1, word count, internal links, images, JSON-LD, and response proxies.
• Preferred-domain checks for HTTP, HTTPS, www, and non-www variants.
• robots.txt, llms.txt, sitemap, key-page, entity, and schema inspection.
• Current-vs-prior artifact search across local audit storage, client storage, and session history.

Unavailable data

• Ahrefs: credential not available. Keyword, backlink, competitor, GSC-through-Ahrefs, and Brand Radar data are [unavailable]. Units burned: 0.
• Google Search Console, GA4, and GBP Insights: no authenticated access was available.
• GBP and map pack: the browser runtime was unavailable, so categories, attributes, reviews, posts, photos, and competitor listings are [unavailable].
• AI answer engines: browser and provider credentials were unavailable. Money-question results are [unavailable].
• Core Web Vitals: PageSpeed Insights returned HTTP 429. Crawl response time and HTML bytes are disclosed proxies only.
• Broken-link sweep: the origin reset connections after the full crawl. Follow-up connection resets were excluded from error totals.

Scoring note

The 43/100 score is a provisional, judgment-weighted health rubric based on observable evidence. It is not a Google, Ahrefs, Lighthouse, or industry-standard score. External-data gaps reduce certainty and are not silently estimated.