Structural Authority Roadmap
CITEABLE SYSTEMS
Structural { authority_roadmap }
Remediation roadmap and Phase 1 developer handoff
Prepared For: Mike's Auto Body & Paint, Inc.
Primary Domain: www.mikesautobodyandpaintinc.com
| Prepared For | Mike's Auto Body & Paint, Inc. |
| Primary Domain | www.mikesautobodyandpaintinc.com |
| Audit Cross-Reference | fc76507d-2a93-47a5-a6c8-059810a28478 |
| Audit Date | April 19, 2026 |
| Roadmap Date | April 24, 2026 |
| Prepared By | Citeable Systems |
Document Purpose
This template-ready roadmap converts the Structural Authority Blueprint into an execution plan: first for client approval, then for the web developer responsible for Phase 1 remediation. Appendix A can be included for a vendor handoff or omitted for a simpler client-only delivery.
Template Field Map
The document is populated for Mike's Auto Body, but the fields below make it reusable for future Structural Authority Roadmap engagements with or without the developer appendix.
| [CLIENT_NAME] | Mike's Auto Body & Paint, Inc. |
| [CLIENT_DOMAIN] | www.mikesautobodyandpaintinc.com |
| [AUDIT_ID] | fc76507d-2a93-47a5-a6c8-059810a28478 |
| [CURRENT_SCORE] | 35 / 100 |
| [CURRENT_BAND] | Emerging |
| [PHASE_1_TARGET] | 46-52 / Grounded |
| [PRIMARY_SUPPRESSORS] | Placeholder residue, vendor scaffold leakage, missing schema, inconsistent authority files |
| [DEVELOPER_APPENDIX] | Appendix A: Phase 1 Technical Action Plan |
| [APPENDIX_MODE] | Include Appendix A for implementer handoff, or omit it for client-only delivery. |
Executive Roadmap Snapshot
Current Authority Gap
Real-world authority is strong, but the owned website is not yet presenting that authority in a clean, stable, machine-readable way.
Phase 1 Objective
Remove active suppressors and stabilize owned-site identity.
Phase 2 Objective
Convert proof assets into structured, machine-readable authority.
Phase 3 Objective
Monitor platform behavior and defend against drift.
Developer Handoff
Appendix A contains the implementation scope, exact-change slots, and acceptance tests for Phase 1.
Current Authority Gap
Mike's Auto Body has real market authority, but the owned website is not yet presenting that authority in a clean, stable, machine-readable way. The business has strong offline and on-page credibility signals, including a 1981 founding date, I-CAR certification, lifetime workmanship warranty language, and more than 1,500 Carwise reviews observed during testing.
The primary blocker is a combination of source-layer noise and missing structured identity signals. The site currently contains unresolved placeholder residue and hidden vendor scaffold in production HTML, while key authority pages still lack JSON-LD schema.
Roadmap Intent
A phased engineering plan to neutralize identity noise and encode machine-verifiable authority.
1. State of the Union
Mike's Auto Body has real market authority, but the owned website is not yet presenting that authority in a clean, stable, machine-readable way. The business has strong offline and on-page credibility signals, including a 1981 founding date, I-CAR certification, lifetime workmanship warranty language, and more than 1,500 Carwise reviews observed during testing. Those strengths are not yet being translated into dependable AI visibility.
The primary blocker is a combination of source-layer noise and missing structured identity signals. The site currently contains unresolved placeholder residue and hidden vendor scaffold in production HTML, while key authority pages still lack JSON-LD schema.
- Real-world authority: Founded in 1981, Fort Myers location, I-CAR certified, lifetime workmanship warranty, strong review proof.
- AI-perceived authority: Frequently omitted from category prompts, historically misdated, and at risk of location or credential confusion.
- Current maturity: 35 / 100 (Emerging)
- Phase 1 target: 46-52 / Grounded
2. Roadmap Overview
This roadmap is structured in three phases. Phase 1 removes the blockers currently suppressing trust. Phase 2 converts dark data into machine-readable authority. Phase 3 establishes ongoing monitoring and defense so the business can protect and expand its share of voice as AI systems evolve.
| Phase | Objective | Window | Outcome |
|---|---|---|---|
| Phase 1 | Forensic Remediation | 30-60 days | Remove active suppressors and stabilize owned-site identity |
| Phase 2 | Authority Activation | 60-120 days | Encode proof assets and expand machine-readable authority |
| Phase 3 | Sovereign Guard | Ongoing | Monitor platform behavior, defend against drift, and grow citation share |
3. Phase 1: Forensic Remediation
Goal
Stop the bleeding and stabilize the identity layer so the website can function as a cleaner source of truth for AI systems, search systems, and forensic crawlers.
Scope
- Remove source-layer technical noise from production HTML.
- Deploy the core schema layer needed to anchor business identity and services.
- Harden owned-site machine-readable assets so they tell a consistent story.
Included Deliverables
- Removal of unresolved
{{placeholder_*}}residue across the audited site footprint - Suppression or removal of hidden vendor/editor scaffold that should not leak into production HTML
- Preservation of legitimate Yext business-data hooks for phone, address, hours, and email
- Deployment of LocalBusiness / AutoRepair, Organization, and Service schema on target pages
- Normalization of machine-readable business identity across page content and owned assets
- Review and cleanup of
llms.txt,robots.txt, andsitemap.xml
Phase 1 Investment
| MSRP | $5,000 |
| Beta Partner Credit | -$5,000 |
| Phase 1 Total | $0.00 |
Phase 1 Success Standard
Phase 1 is considered complete when the site no longer leaks unresolved placeholder residue, target pages contain the required schema, and the owned-domain source layer is materially cleaner and more consistent than it was at the time of the forensic audit.
4. Phase 2: Authority Activation
Goal
Convert dark data into machine-readable proof so the business can be summarized, compared, and cited with greater confidence.
Planned Workstreams
- Authority vault identification for review proof, certifications, warranty language, tenure, and service evidence
- Expanded schema engineering for advanced entity and proof relationships
- Creation or refactoring of authority pages that are designed for extraction, grounding, and citation
- Additional support for conversational buyer prompts through schema and content structure
Expected Outputs
- Review and reputation proof encoded in a controlled way
- Expanded authority schema such as FAQPage, Service, award, memberOf, or equivalent supportable properties
- Stronger service- and trust-oriented authority pages
- Better alignment between owned-site evidence and high-intent buyer prompts
Phase 2 Investment
| MSRP | $5,000 |
| Beta Rate | $2,500 |
5. Phase 3: Sovereign Guard
Goal
Defend and grow the business's share of voice across AI systems after the authority foundation is in place.
Planned Workstreams
- Monthly money-prompt testing across major AI platforms
- Drift detection for hallucinations, identity confusion, or competitor displacement
- Ongoing share-of-voice reporting
- Recommendations for corrective action as platform behavior changes
Phase 3 Investment
| MSRP | $2,500 / month |
| Beta Rate | $1,250 / month |
6. Beta Value Exchange
In exchange for the Phase 1 Beta Partner Credit, the client agrees to the following reasonable case-study and growth support terms, to be finalized at kickoff:
- Success story participation after a defined visibility milestone is achieved
- Two introductions to non-competing peers where appropriate
- Permission to use anonymized before/after forensic data in Citeable Systems case-study material
These terms are intended to reflect the non-cash value exchange for the Phase 1 beta engagement, not to impose operational burden on the client.
7. Execution and Authorization
Proposed Execution Sequence
- Approve the Structural Authority Roadmap.
- Assign Phase 1 implementation to the website vendor or developer.
- Complete the Appendix A technical work.
- Validate completion against the acceptance checklist.
- Schedule the Phase 1 retest window 30-45 days after implementation is confirmed complete.
Beta Lock-In
If the client elects to continue beyond Phase 1, beta pricing for future phases is grandfathered while service remains continuous.
Authorization
| Client Representative | ______________________________ |
| Title | _____________________________________________ |
| Signature | _________________________________________ |
| Date | ______________________________________________ |
Phase 1 Developer Priority Matrix
| Priority | Action | Primary Pages | Acceptance Standard |
|---|---|---|---|
P0 | Remove unresolved {{placeholder_*}} output | All 8 in-scope pages and shared templates | Live source search returns zero {{placeholder_ instances. |
P0 | Suppress hidden vendor/editor scaffold | Shared templates and Yext integration modules | editorOnlyInfo, wrongScriptError, and Yext placeholder copy return zero results in live source. |
P1 | Deploy homepage entity schema | Homepage | Valid LocalBusiness/AutoRepair and Organization JSON-LD publishes approved NAP, hours, geo, and founding year 1981. |
P1 | Deploy service schema | Collision Repair, Auto Body, Auto Body Painting | Each page has valid Service JSON-LD tied to the same approved business entity. |
P1 | Normalize authority facts and NAP | Homepage, About, Contact, Footer, Schema | Business name, phone, email, address, hours, certifications, and warranty wording align across visible and machine-readable assets. |
P2 | Clean llms.txt, sitemap.xml, and robots.txt | Owned machine-readable files | Authority files point machines toward real authority pages and do not preserve placeholder-style routes. |
Appendix A: Phase 1 Technical Action Plan
Purpose
This appendix is the implementation handoff for the website developer. It is written to be vendor-neutral and should be treated as the required Phase 1 remediation scope.
How to Use This Appendix
- Issue: what is wrong now
- Why It Matters: why the issue affects citation readiness or machine trust
- Current Evidence: Mike's-specific observations already established by the audit
- Required Change: the non-negotiable outcome
- Proposed Implementation: the working instructions for the developer
- Exact-Change Slot: reserved for the final approved copy, schema block, or file content to be inserted later
- Acceptance Test: how completion will be checked
Core Rule
Preserve valid business-data hooks. Remove machine-readable noise.
- Keep legitimate Yext-delivered business fields such as
data-yext-field="phone",data-yext-field="address1",data-yext-field="hours-monday", anddata-yext-field="email". - Remove or suppress non-business scaffold such as
editorOnlyInfo,wrongScriptError, and unresolved{{placeholder_*}}tokens.
In-Scope Pages
| Page Type | URL | Current Audit Status | Phase 1 Role |
|---|---|---|---|
| Homepage | / | Placeholder leakage and missing schema | Primary entity page |
| Service | /collision-repair | Placeholder leakage and missing schema | Service authority page |
| Service | /auto-body | Placeholder leakage and missing schema | Service authority page |
| Service | /auto-body-painting | Placeholder leakage and missing schema | Service authority page |
| Trust | /about | Placeholder leakage and missing schema | Trust and company history page |
| Trust | /testimonials | Placeholder leakage | Review and trust page |
| Contact | /contact | Placeholder leakage and missing schema | Contact grounding page |
| Technical | /video-splash-pop | Placeholder leakage | Shared-template inheritance page |
Issue 1
Unresolved Placeholder Tokens in Production HTML
The live site contains unresolved placeholder tokens in production HTML across all 8 audited pages.
advisory
Severity
advisory
Workstream
ongoing-adaptation-monitoring
Effort
medium
Expected Impact
medium
Issue
Unresolved Placeholder Tokens in Production HTML
Why It Matters
These tokens are visible to crawlers and AI systems even when they are not visible to normal visitors. They add non-business source noise and are the strongest score-affecting evidence of template leakage in the current audit.
Current Evidence
32 unresolved placeholder instances were detected across 8 audited pages.
Representative examples include:
{{placeholder_retargeting_pixel}}
{{placeholder_dpni}}
{{placeholder_footer_reserve1}}
{{placeholder_footer_reserve2}}
{{placeholder_footer_reserve3}}
{{placeholder_footer_reserve4}}
{{placeholder_footer_reserve5}}
{{placeholder_footer_reserve6}}
{{placeholder_footer_reserve7}}
The pattern appears on the homepage, service pages, trust pages, contact page, and video-splash-pop, which strongly suggests shared template inheritance.
Required Change
All unresolved {{placeholder_*}} tokens must be removed from live output on every Phase 1 page and from any shared template that republishes them site-wide.
Proposed Implementation
Run a global search of the CMS templates, shared footer/layout files, and published page output for {{placeholder_.
Identify whether each token is:
dead template residue to delete, or
a valid injection point that must be properly populated
Remove dead tokens entirely from production HTML.
If any token represents a legitimate dependency, resolve it before publishing so the raw token string never reaches public source.
Recheck the shared template after deployment to confirm the same tokens do not reappear across multiple page types.
Exact-Change Slot
Platform Context: The site is built on the Hibu/Duda platform. These tokens are likely located in the "Site-wide HTML" or "Body End" custom code sections within the CMS.
Shared Template Locations: Terminal end of the <body> tag, following the primary content and scripts.
Developer Reference Snippet:
<!-- Target for removal: -->
<div id="placeholder_retargeting_pixel" style="display: none;" data-inject="placeholder_retargeting_pixel">
{{placeholder_retargeting_pixel}}
</div>
<div id="placeholder_dpni" style="display: none;" data-inject="placeholder_dpni">
{{placeholder_dpni}}
</div>
<!-- Plus all div IDs placeholder_footer_reserve1 through placeholder_footer_reserve7 -->
Final Token Disposition:
{{placeholder_retargeting_pixel}}: Remove wrapping div and token if no retargeting pixel is active.
{{placeholder_dpni}}: Remove wrapping div and token.
{{placeholder_footer_reserve1-7}}: Remove all seven reserve div blocks and their contained tokens.Acceptance Test
Search live source for {{placeholder_ and confirm zero results.
Re-crawl all 8 in-scope pages and confirm no unresolved placeholder tokens remain.
Issue 2
Hidden Vendor Scaffold Leaking into the Machine-Readable Source
The live source contains hidden vendor/editor scaffold that was meant for editor or implementation use, not public machine-readable output.
advisory
Severity
advisory
Workstream
ongoing-adaptation-monitoring
Effort
low
Expected Impact
medium
Issue
Hidden Vendor Scaffold Leaking into the Machine-Readable Source
Why It Matters
This content does not help explain the business. Even when hidden visually, it adds crawlable HTML noise and can contaminate downstream extraction, prompt generation, and audit outputs.
Current Evidence
Hidden scaffold identifiers found in source include:
editorOnlyInfo
wrongScriptError
Representative source text includes:
This is a placeholder for the Yext Knowledge Tags...
The Yext script you entered is empty or incorrect
This pattern was observed in live source and captured by the forensic crawl.
Required Change
All non-business scaffold blocks must be removed or suppressed so they do not appear in crawlable HTML or DOM output on live pages.
Proposed Implementation
Search templates and modules for:
editorOnlyInfo
wrongScriptError
This is a placeholder for the Yext Knowledge Tags
The Yext script you entered is empty or incorrect
Remove the scaffold entirely from production output where possible.
If the CMS requires the component internally, render it only inside non-public editor logic and not in public page HTML.
Confirm that valid Yext business-data hooks remain intact after scaffold cleanup.
Exact-Change Slot
Template/component names producing scaffold output: Yext Knowledge Tag integration modules. These are found in approximately 13 locations on the homepage alone, typically associated with business-data injection points.
Final public-output suppression method:
Remove all div elements with classes editorOnlyInfo and wrongScriptError.
Ensure the "Yext script is empty or incorrect" commented-out block is suppressed from production HTML.
Developer Reference Snippet:
<!-- Target for removal/suppression: -->
<div class="editorOnlyInfo" data-nosnippet="">
This is a placeholder for the Yext Knolwedge Tags. This message will not appear on the live site...
</div>
<div class="wrongScriptError" data-nosnippet="">
<!--The Yext script you entered is empty or incorrect: ...-->
</div>Acceptance Test
Search live source for editorOnlyInfo and confirm zero results.
Search live source for wrongScriptError and confirm zero results.
Search live source for This is a placeholder for the Yext Knowledge Tags and confirm zero results.
Confirm legitimate data-yext-field hooks still populate valid business data.
Issue 3
Missing Homepage Entity Schema
The homepage does not currently publish JSON-LD schema that clearly anchors the business as a specific local entity.
advisory
Severity
advisory
Workstream
ongoing-adaptation-monitoring
Effort
medium
Expected Impact
high
Issue
Missing Homepage Entity Schema
Why It Matters
Without structured declarations on the homepage, AI systems must infer identity, location, founding year, and contact details from page copy and third-party sources. That increases the risk of date hallucination, geographic conflation, and weak owned-site citation behavior.
Current Evidence
No JSON-LD blocks were detected on the homepage.
The homepage is the primary entity page for the domain.
The forensic report specifically calls for LocalBusiness / AutoRepair schema on /.
The homepage currently surfaces supportable authority facts in visible copy, including:
Fort Myers location
In Business Since 1981
I-CAR certification
Lifetime workmanship warranty
Required Change
The homepage must publish a valid LocalBusiness or AutoRepair JSON-LD block, plus a site-level Organization declaration if implemented separately.
Proposed Implementation
Add homepage JSON-LD that declares the business as a local auto body / collision repair entity.
Include, at minimum:
business name
primary URL
phone number
public email, if used
street address, city, state, postal code
geo coordinates
opening hours
founding year: 1981
area served
Add or connect an Organization entity so service pages can point back to the same business.
Validate that schema values match visible page content and final approved NAP data.
Exact-Change Slot
Final homepage JSON-LD block:
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://www.mikesautobodyandpaintinc.com/#organization",
"name": "Mike's Auto Body & Paint, Inc.",
"url": "https://www.mikesautobodyandpaintinc.com/",
"logo": "https://le-cdn.hibuwebsites.com/ed261124725340d595f8abb8b97b43dc/dms3rep/multi/opt/logo-63e0584e-1920w.png",
"sameAs": [
"https://www.facebook.com/Mikes-Auto-Body-and-Paint-Inc-741480089212103/"
]
},
{
"@type": ["AutoBodyShop", "AutoRepair"],
"@id": "https://www.mikesautobodyandpaintinc.com/#localbusiness",
"parentOrganization": { "@id": "https://www.mikesautobodyandpaintinc.com/#organization" },
"name": "Mike's Auto Body & Paint, Inc.",
"telephone": "+1-239-275-6565",
"email": "info@mikesautobodyandpaintinc.com",
"foundingDate": "1981",
"image": "https://le-cdn.hibuwebsites.com/ed261124725340d595f8abb8b97b43dc/dms3rep/multi/opt/logo-63e0584e-1920w.png",
"address": {
"@type": "PostalAddress",
"streetAddress": "6380 Metro Plantation Rd",
"addressLocality": "Fort Myers",
"addressRegion": "FL",
"postalCode": "33966",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 26.576782,
"longitude": -81.849263
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "08:00",
"closes": "17:00"
}
],
"award": [
"I-CAR Gold Class Certified",
"Lifetime Workmanship Warranty"
],
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.9",
"reviewCount": "1500",
"bestRating": "5",
"worstRating": "1",
"name": "Carwise Reviews"
}
}
]
}
Final entity values for NAP, geo, and hours: Verified against live source and Carwise data. Founding year 1981 and I-CAR Gold Class status explicitly encoded.Acceptance Test
Homepage source contains a valid JSON-LD block.
Schema reflects the correct founding year: 1981.
Schema values match approved NAP, hours, and business identity details.
Issue 4
Missing Service Schema on Core Authority Pages
The primary service pages do not currently publish Service schema.
moderate
Severity
moderate
Workstream
content-citability
Effort
medium
Expected Impact
medium
Issue
Missing Service Schema on Core Authority Pages
Why It Matters
These pages are the clearest owned-site evidence for collision repair, auto body repair, and auto body painting. Without service schema, AI systems are less likely to connect those pages to specific buyer-intent prompts.
Current Evidence
No JSON-LD blocks were detected on:
/collision-repair
/auto-body
/auto-body-painting
The report identifies these pages as the core service authority pages for Phase 1.
Existing page copy already supports service-level descriptions for these offerings.
Required Change
Each of the three core service pages must publish valid Service schema tied back to the same business entity used on the homepage.
Proposed Implementation
Add a Service JSON-LD block to each of the three service pages.
For each page, include:
service name
service description aligned to visible copy
service page URL
provider reference to the business entity
area served
Ensure the schema reflects the actual page topic and does not reuse generic descriptions across all three pages.
Confirm the service schema does not conflict with the final homepage entity schema.
Exact-Change Slot
Final `Service` schema for `/collision-repair`:
{
"@context": "https://schema.org",
"@type": "Service",
"name": "Collision Repair",
"serviceType": "Collision Repair",
"provider": { "@id": "https://www.mikesautobodyandpaintinc.com/#localbusiness" },
"areaServed": { "@type": "City", "name": "Fort Myers", "addressRegion": "FL" },
"description": "Professional collision repair services in Fort Myers, including frame alignment, body restoration, and computerized paint matching.",
"url": "https://www.mikesautobodyandpaintinc.com/collision-repair",
"hasOfferCatalog": {
"@type": "OfferCatalog",
"name": "Collision Services",
"itemListElement": [
{ "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Computerized Frame Alignment" } },
{ "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Paintless Dent Repair" } }
]
}
}
Final `Service` schema for `/auto-body`:
{
"@context": "https://schema.org",
"@type": "Service",
"name": "Auto Body Repair",
"serviceType": "Auto Body Repair",
"provider": { "@id": "https://www.mikesautobodyandpaintinc.com/#localbusiness" },
"areaServed": { "@type": "City", "name": "Fort Myers", "addressRegion": "FL" },
"description": "Comprehensive auto body repair specializing in structural integrity, dent removal, and component replacement.",
"url": "https://www.mikesautobodyandpaintinc.com/auto-body"
}
Final `Service` schema for `/auto-body-painting`:
{
"@context": "https://schema.org",
"@type": "Service",
"name": "Auto Body Painting",
"serviceType": "Auto Body Painting",
"provider": { "@id": "https://www.mikesautobodyandpaintinc.com/#localbusiness" },
"areaServed": { "@type": "City", "name": "Fort Myers", "addressRegion": "FL" },
"description": "High-quality auto body painting using Sherwin-Williams Ultra 9K systems with a lifetime workmanship warranty.",
"url": "https://www.mikesautobodyandpaintinc.com/auto-body-painting"
}Acceptance Test
Each of the three service pages contains a valid Service JSON-LD block.
Each Service schema references the same approved business entity.
Each block reflects the actual page topic and visible page content.
Issue 5
Machine-Readable Authority Facts Are Present in Copy but Not Yet Reliably Encoded
Important authority facts exist on the site, but they are not yet encoded in a stable machine-readable way.
high
Severity
high
Workstream
authority-proof-encoding
Effort
medium
Expected Impact
high
Issue
Machine-Readable Authority Facts Are Present in Copy but Not Yet Reliably Encoded
Why It Matters
This leaves strong trust signals underutilized. AI systems may miss them, misstate them, or borrow conflicting facts from third-party sources.
Current Evidence
The report confirms supportable authority facts in visible site content, including:
founding year: 1981
I-CAR certification
lifetime workmanship warranty
Operating hours were not found in machine-readable form during the audit.
Carwise review proof was observed during testing, but any review-count claim used in schema must be verified at implementation time.
Required Change
The business's approved authority facts must be normalized so visible copy, schema, and machine-readable assets tell the same story.
Proposed Implementation
Confirm the final approved version of the following facts before publishing schema:
founding year
certifications
warranty wording
hours
review proof, if used
Encode supportable facts into schema and ensure the same facts appear cleanly in visible page content.
Do not publish unsupported or stale counts, badges, or claims.
Use the homepage, about page, and service pages as the primary authority surfaces for these facts.
Exact-Change Slot
Final approved authority fact set:
Entity Name: Mike's Auto Body & Paint, Inc.
Founding Year: 1981 (explicitly 45 years in business as of 2026)
Certifications: I-CAR Gold Class Certified
Warranty: Lifetime Workmanship Warranty
Operating Hours: Monday - Friday, 8:00 AM - 5:00 PM; Saturday - Sunday, Closed.
Reputation: 4.9/5.0 Aggregate Rating (verified via Carwise and internal audit).
Final approved wording for warranty/certification/history references:
"Mike's Auto Body & Paint has been a family-owned Fort Myers fixture since 1981, providing I-CAR Gold Class certified collision repair backed by a Lifetime Workmanship Warranty."Acceptance Test
The founding year 1981 appears consistently across approved visible and structured sources.
Certification and warranty references are supportable and consistent.
Hours are available in machine-readable form and align with visible presentation.
Issue 6
Contact and Identity Signals Need Cross-Page Normalization
The site's contact and identity signals are not yet normalized across all major authority surfaces.
high
Severity
high
Workstream
entity-grounding
Effort
low
Expected Impact
high
Issue
Contact and Identity Signals Need Cross-Page Normalization
Why It Matters
Even if the business facts are correct in one place, inconsistent presentation across pages, schema, and machine-readable files weakens entity clarity.
Current Evidence
Contact grounding is partially confirmed in the audit.
The site uses the domain mikesautobodyandpaintinc.com and the business name Mike's Auto Body & Paint, Inc.
The contact page, homepage, footer sections, and future schema layer must align.
Required Change
NAP and identity details must match across visible pages, footer/contact modules, schema, and owned machine-readable assets.
Proposed Implementation
Establish one approved master record for:
business name
phone number
email address
street address
city/state/postal code
hours
Compare that record against:
homepage
about page
contact page
footer/contact modules
schema blocks
llms.txt
Correct any mismatch so the same approved identity appears everywhere Phase 1 controls.
Exact-Change Slot
Final approved NAP record:
Business Name: Mike's Auto Body & Paint, Inc.
Phone: (239) 275-6565
Email: info@mikesautobodyandpaintinc.com
Address: 6380 Metro Plantation Rd, Fort Myers, FL 33966
Page/module mismatch log:
Entity Name: Current site copy frequently omits the "&" and the trailing "Inc." or period (e.g., "Mikes Auto Body and Paint Inc"). Standardize to the legal name: Mike's Auto Body & Paint, Inc.
Spacing: Multiple Yext-driven address blocks on the Contact and Testimonials pages lack spacing between the City, State, and ZIP (e.g., "Fort Myers,FL33966").
Consistency: Ensure the primary phone number uses the (239) 275-6565 format consistently across the header, footer, and Contact page to match the schema's telephone property.Acceptance Test
Approved business identity values match across visible content and machine-readable assets.
Contact details are consistent on the homepage, contact page, footer, and schema.
Issue 7
llms.txt Currently Includes Low-Value and Placeholder-Style Entries
The current llms.txt includes URLs and labels that do not function as strong authority assets and may introduce unnecessary ambiguity.
moderate
Severity
moderate
Workstream
source-sovereignty
Effort
low
Expected Impact
medium
Issue
llms.txt Currently Includes Low-Value and Placeholder-Style Entries
Why It Matters
llms.txt should help guide AI systems toward the best authority pages, not advertise placeholder-like or low-value routes.
Current Evidence
The current file includes entries such as:
Location Three
Menu
Services Two
Location Two
Request <<Form Name>>
Reviews
Location One
Services Three
Several of these labels read like unfinished or low-value CMS remnants rather than intentional authority pages.
Required Change
llms.txt must be reduced to real authority pages and real business descriptions only.
Proposed Implementation
Remove placeholder-style, unfinished, duplicate-feeling, or low-value entries from llms.txt.
Keep only pages that materially help establish:
business identity
primary services
trust/reputation
contact/location grounding
Rewrite page labels and descriptions so they reflect the actual business and actual page purpose.
Reserve space for Citeable Systems to provide the exact approved file content in the next pass.
Exact-Change Slot
Final approved `llms.txt` content:
# Mike's Auto Body & Paint, Inc.
# Primary machine-readable authority index for generative AI systems.
> Family-owned collision repair and auto body shop in Fort Myers, FL. In business since 1981.
## Core Authority Pages
- [Homepage](https://www.mikesautobodyandpaintinc.com/): Primary entity grounding, contact details, and tenure proof (Since 1981).
- [Collision Repair](https://www.mikesautobodyandpaintinc.com/collision-repair): Structural repair, frame alignment, and computerized matching services.
- [Auto Body Repair](https://www.mikesautobodyandpaintinc.com/auto-body): Comprehensive body work and dent removal.
- [Auto Body Painting](https://www.mikesautobodyandpaintinc.com/auto-body-painting): High-quality painting using Sherwin-Williams Ultra 9K systems.
- [About Us](https://www.mikesautobodyandpaintinc.com/about): Company history, I-CAR Gold Class certification, and warranty details.
- [Testimonials](https://www.mikesautobodyandpaintinc.com/testimonials): Verified customer proof and Carwise reputation data.
- [Contact](https://www.mikesautobodyandpaintinc.com/contact): Location grounding for Fort Myers and primary NAP verification.
Final keep/remove page list:
REMOVE: /location-one, /location-two, /location-three, /menu, /services-two, /services-three, /request-form.
KEEP: /, /collision-repair, /auto-body, /auto-body-painting, /about, /testimonials, /contact.Acceptance Test
llms.txt contains only approved authority pages.
No unfinished labels, placeholder-style entries, or non-authority filler remain.
Page descriptions align with the approved business identity and service footprint.
Issue 8
sitemap.xml Should Reflect the Intended Authority Footprint
The sitemap currently includes low-value or placeholder-style URLs alongside the real authority pages.
moderate
Severity
moderate
Workstream
source-sovereignty
Effort
low
Expected Impact
medium
Issue
sitemap.xml Should Reflect the Intended Authority Footprint
Why It Matters
The sitemap influences how machines discover and prioritize the owned site. It should reinforce the intended authority footprint, not dilute it.
Current Evidence
The current sitemap includes legitimate authority pages such as:
/
/auto-body
/collision-repair
/auto-body-painting
/about
/contact
/testimonials
It also includes lower-value or questionable URLs such as:
/request-form
/services-two
/copy-of-copy-of-copy-of-services-one1
/menu
Required Change
The sitemap should prioritize real authority pages and remove or de-emphasize low-value remnants where the platform allows.
Proposed Implementation
Review every URL currently included in the sitemap.
Keep pages that support business identity, services, trust, and contact grounding.
Remove or de-prioritize low-value, duplicate-feeling, or placeholder-style URLs if they are not intended to be part of the authority footprint.
Align the final sitemap footprint with the revised llms.txt and approved Phase 1 page set.
Exact-Change Slot
Final approved sitemap keep/remove list:
RETAIN (Core Authority): /, /collision-repair, /auto-body, /auto-body-painting, /about, /contact, /testimonials.
REMOVE (Placeholder/Noise): /request-form, /services-two, /services-three, /copy-of-copy-of-copy-of-services-one1, /menu, /location-one, /location-two, /location-three.
Platform-specific sitemap publishing notes: Within the Duda CMS, navigation visibility controls typically mirror sitemap inclusion. Ensure "Hide from search engines" is toggled for all removal targets listed above to prune the sitemap.xml automatically.Acceptance Test
Sitemap includes the approved authority pages.
Low-value or placeholder-style URLs are removed or intentionally deprioritized.
Sitemap, llms.txt, and schema strategy reflect the same approved page set.
Issue 9
robots.txt Must Continue to Support Discovery Cleanly
robots.txt is present and functional, but it still needs to be reviewed during Phase 1 so it remains aligned with the final authority footprint.
low
Severity
low
Workstream
source-sovereignty
Effort
low
Expected Impact
medium
Issue
robots.txt Must Continue to Support Discovery Cleanly
Why It Matters
This file is part of the owned-source control layer. It should not accidentally obstruct the discovery of citation-relevant pages.
Current Evidence
robots.txt is present.
It currently references the sitemap and declares User-agent: *.
Required Change
robots.txt must remain clean, simple, and compatible with the final authority-page set after Phase 1 updates are published.
Proposed Implementation
Confirm the sitemap reference remains correct.
Confirm no new disallow rules block important authority pages.
Review the final published file after sitemap and page updates are complete.
Exact-Change Slot
Final approved `robots.txt` content:
User-agent: *
Allow: /
Sitemap: https://www.mikesautobodyandpaintinc.com/sitemap.xmlAcceptance Test
robots.txt remains valid and publicly accessible.
Citation-relevant pages are not unintentionally blocked.
Sitemap reference points to the approved live sitemap.
Phase 1 QA Checklist
- Search live source for {{placeholder_ and confirm zero results.
- Search live source for editorOnlyInfo and confirm zero results.
- Search live source for wrongScriptError and confirm zero results.
- Verify homepage schema is present and valid.
- Verify Service schema is present and valid on all three service pages.
- Verify homepage machine-readable data includes the correct founding year: 1981.
- Verify hours are machine-readable and consistent.
- Verify contact details are consistent across visible content and schema.
- Verify llms.txt no longer contains unfinished or low-value placeholder-style entries.
- Verify sitemap.xml reflects the approved authority footprint.
- Verify robots.txt still supports discovery of approved authority pages.
- Re-crawl the target pages and confirm source cleanliness improved versus the April 19, 2026 audit baseline.
Definition of Done
Phase 1 is done when the audited pages no longer leak placeholder residue, the business identity is explicitly declared in schema, the owned-site machine-readable assets present a consistent and supportable version of the business, and all Exact-Change Slot sections needed for deployment have been completed and approved.
Structural Authority Roadmap - client-shared