Demo data — fictional demonstration report
RankInAI
AI Visibility & GEO Audit Report
Atlas Roofing & Exteriors
https://www.atlasroofingexteriors.example
- Audit date
- April 18, 2026
- Pages analyzed
- 10
- Industry
- Construction and trades
- Target market
- United States
Good
Overall AI Visibility Score
Overall AI Visibility Score: 72/100 (Good)
This website is in reasonable shape for AI visibility. The fundamentals are present, but specific gaps are limiting how confidently an answer engine could describe or cite the business.
Previous audit: 65 (+7)
Executive summary
Atlas Roofing & Exteriors scores 72 out of 100 for AI visibility readiness, based on 10 pages crawled from www.atlasroofingexteriors.example. The site is technically sound and unusually strong on trust signals: complete contact details, a stated Colorado license number and a 2004 founding date all appear site-wide and match the LocalBusiness schema exactly. The limiting factor is structure rather than substance. Fourteen genuine question-and-answer pairs already exist across three pages but carry no FAQPage markup, so an answer engine has to infer them from headings. Service pages average 380 words with no pricing, process or outcome detail, and every page on the site is published anonymously. The three "Do first" actions below are all low or medium effort and address content that already exists — they make it machine-readable rather than requiring anything new to be written.
Category scores
Technical Accessibility
15% of the overall score
The site is fully reachable over HTTPS, indexable and served quickly. A missing llms.txt and two broken internal links are the only outstanding items.
Entity Clarity
17% of the overall score
The business name, service area and audience are all stated, but four service pages share a near-identical title pattern and the About page is thin at 210 words.
Content Authority
18% of the overall score
Service pages average 380 words and lean on marketing phrasing. There are no case studies and only three dated articles in the last two years.
Answer Readiness
17% of the overall score
Only six question-led headings were found across ten pages, and the existing FAQ content is not marked up, so it cannot be read as question/answer pairs.
Structured Data
13% of the overall score
LocalBusiness schema is present and valid but incomplete — no sameAs links, no areaServed and no FAQPage markup anywhere on the site.
Trust and Evidence
15% of the overall score
Full contact details, a license number and a founding year are published. Content is largely unattributed, which is the main remaining gap.
Competitive Visibility
5% of the overall score
Ahead of the sampled competitor on trust signals, behind on structured data coverage and question-led content.
Key strengths and critical weaknesses
Key strengths
- Complete NAP details published in the footer of every page and mirrored in LocalBusiness schema
- Every page is served over HTTPS, indexable, and returns in under 700ms
- Colorado roofing license number and 2004 founding date are stated prominently
Critical weaknesses
- No FAQPage structured data anywhere, despite an existing FAQ section on three pages
- Service pages average 380 words with no pricing, process detail or specific outcomes
- No named author on any page — all content is anonymous
Technical Accessibility
Score 86/100Whether AI crawlers and answer engines can reach, load and index your pages at all. The site is fully reachable over HTTPS, indexable and served quickly. A missing llms.txt and two broken internal links are the only outstanding items.
Every page is served over HTTPS
tech.https
HTTPS is the baseline requirement for being treated as a trustworthy source by AI crawlers.
Evidence observed on your website
- pagesChecked
- 10
- pagesOverHttps
- 10
- certificateValid
- yes
https://www.atlasroofingexteriors.example/
No llms.txt guidance file published
tech.llms-txt
llms.txt is an emerging convention for pointing language models at the pages that best summarize a site. Adoption is early, so its absence is not penalized heavily.
Recommended action
Consider publishing /llms.txt with a short business description and links to the most useful pages.
Effort: lowImpact: low
Evidence observed on your website
- found
- no
- checkedUrl
- /llms.txt
Entity Clarity
Score 74/100How unambiguously your site states who the business is, what it does and who it serves. The business name, service area and audience are all stated, but four service pages share a near-identical title pattern and the About page is thin at 210 words.
About page is too thin to define the organization
entity.about-page
The About page confirms the founding year but says nothing about leadership, team size, certifications or specialization. This is the page a model looks to when confirming who is behind the content.
Recommended action
Expand the About page to at least 500 words covering leadership, crew size, certifications, insurance, the specific service area and what the business specializes in.
Effort: mediumImpact: high
Evidence observed on your website
- aboutPageUrl
- /about
- wordCount
- 210
- mentionsFoundingOrHistory
- yes
- mentionsTeam
- no
- mentionsCredentials
- no
https://www.atlasroofingexteriors.example/about
Answer Readiness
Score 58/100How easily individual passages can be extracted as direct answers to real questions. Only six question-led headings were found across ten pages, and the existing FAQ content is not marked up, so it cannot be read as question/answer pairs.
FAQ content exists but is not machine-readable
answer.faq-coverage
Fourteen question/answer pairs were found across three pages, but none are marked up with FAQPage schema. Without the markup, an answer engine has to infer the structure from headings, which is far less reliable.
Recommended action
Add FAQPage JSON-LD to the /faq page and to the FAQ blocks on the two service pages, mapping each visible question to its answer text.
Effort: lowImpact: high
Evidence observed on your website
- faqSectionsFound
- 3
- pagesWithFaqContent
- /faq, /services/roof-replacement, /storm-damage
- faqPageSchemaPresent
- no
- questionsDetected
- 14
https://www.atlasroofingexteriors.example/faq
Structured Data
Score 69/100Machine-readable schema markup describing your organization, content and offerings. LocalBusiness schema is present and valid but incomplete — no sameAs links, no areaServed and no FAQPage markup anywhere on the site.
LocalBusiness schema is missing key properties
schema.organization-completeness
The block is valid but carries only four properties. sameAs and areaServed in particular are what let an entity-resolution system connect this business to its other public profiles and its service region.
Recommended action
Extend the existing LocalBusiness block with logo, description, email, areaServed and a sameAs array of verified profiles.
Effort: lowImpact: high
Evidence observed on your website
- propertiesPresent
- name, url, telephone, address
- valuableMissing
- logo, description, sameAs, areaServed, email
- schemaValid
- yes
https://www.atlasroofingexteriors.example/
Trust and Evidence
Score 81/100Authorship, contact details, citations and proof that support what the site claims. Full contact details, a license number and a founding year are published. Content is largely unattributed, which is the main remaining gap.
No content is attributed to a named person
trust.author-attribution
Named authors let a system attach expertise and accountability to a claim. Every page on this site is anonymous, so nothing published here can be weighed as expert testimony.
Recommended action
Add a byline with a real name and credentials to every substantive page, linked to a bio page, and express it in Person schema.
Effort: mediumImpact: high
Evidence observed on your website
- authorsFound
- none
- pagesWithByline
- 0
- editorialPages
- 3
- personSchemaPresent
- no
https://www.atlasroofingexteriors.example/blog/ice-dam-prevention
Complete contact details are published site-wide
trust.contact-details
A verifiable phone number, email and postal address are among the strongest signals that a site represents a real operating business.
Evidence observed on your website
- emailFound
- yes
- phoneFound
- yes
- postalAddressFound
- yes
- matchesSchema
- yes
- sampleAddress
- 4820 Kalamath St, Denver, CO 80211
https://www.atlasroofingexteriors.example/contact
Competitor comparison
Overall comparison
Competitor scores are derived from a single public homepage fetch, not a full crawl. They compare homepage-level signals only.
Summit Peak Roofing
https://www.summitpeakroofing.example
What they do well
- Declares 5 schema types including FAQPage and BreadcrumbList
- 11 question-led headings on the homepage
- Publishes a last-updated date on every service page
Where they are weak
- No postal address published anywhere on the site
- Homepage copy is thinner (418 words)
- No license number or founding date stated
Prioritized action plan
Do first3 actions
High-impact fixes that remove barriers or add missing fundamentals. Most can be completed in a single working session.
- 1
Publish and mark up an FAQ
Answer Readiness
high impactlow effort- Why it matters
- Fourteen genuine question/answer pairs already exist on the site but are invisible as structured data. FAQPage markup is the lowest-effort change here with a direct effect on how retrievable those answers are.
- Exact recommended change
- Add FAQPage JSON-LD to /faq and to the FAQ blocks on the roof-replacement and storm-damage pages. Map each visible question to its exact answer text — never mark up a question that is not on the page.
- Example implementation
{ "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{ "@type": "Question", "name": "How long does a roof replacement take?", "acceptedAnswer": { "@type": "Answer", "text": "Most residential replacements in the Denver metro take one to two days. Steeper pitches, tile and metal systems, and jobs needing deck repair can run to four days." } }] }- Expected impact
- Closing this gap contributes a meaningful improvement to your Answer Readiness score (8.0 of 8 points currently unearned).
- 2
Complete your LocalBusiness schema properties
Structured Data
high impactlow effort- Why it matters
- Your schema block is valid but carries only four properties. sameAs and areaServed are what let an entity-resolution system connect this business to its other public profiles and confirm the region it serves.
- Exact recommended change
- Extend the existing LocalBusiness block — do not add a second one — with logo, description, email, areaServed and a sameAs array of verified profiles.
- Example implementation
{ "@context": "https://schema.org", "@type": "RoofingContractor", "name": "Atlas Roofing & Exteriors", "url": "https://www.atlasroofingexteriors.example", "logo": "https://www.atlasroofingexteriors.example/logo.png", "description": "Licensed roofing contractor serving the Denver metro area since 2004.", "telephone": "+1-303-555-0142", "email": "hello@atlasroofingexteriors.example", "address": { "@type": "PostalAddress", "streetAddress": "4820 Kalamath St", "addressLocality": "Denver", "addressRegion": "CO", "postalCode": "80211", "addressCountry": "US" }, "areaServed": ["Denver", "Aurora", "Lakewood", "Arvada", "Boulder", "Westminster"], "sameAs": [ "https://www.linkedin.com/company/atlas-roofing-exteriors", "https://www.bbb.org/us/co/denver/profile/roofing/atlas-roofing-exteriors" ] }- Expected impact
- Closing this gap contributes a meaningful improvement to your Structured Data score (4.5 of 8 points currently unearned).
- 3
Attribute content to named authors
Trust and Evidence
high impactmedium effort- Why it matters
- Every page on the site is anonymous. Named authors with stated credentials let a system treat your guidance as expert testimony rather than unattributed marketing copy.
- Exact recommended change
- Add a byline with a real name and license number to every substantive page, link it to a bio page, and express it in Person schema.
- Example implementation
<p class="byline"> Written by <a href="/team/marcus-vail">Marcus Vail</a>, Master Roofer, CO License #RC-44821 — 18 years in commercial roofing. </p>
- Expected impact
- Closing this gap contributes a large improvement to your Trust and Evidence score (8.0 of 8 points currently unearned).
Next 30 days3 actions
Meaningful improvements that need coordination or content work but no structural change.
- 4
Build out a substantive About page
Entity Clarity
high impactmedium effort- Why it matters
- The About page is the page a model looks to when confirming the organization behind the content. At 210 words it confirms a founding year and nothing else.
- Exact recommended change
- Expand the About page to at least 500 words covering leadership, crew size, certifications, insurance, the exact service area and what the business specializes in.
- Expected impact
- Closing this gap contributes a meaningful improvement to your Entity Clarity score (2.8 of 8 points currently unearned).
- 5
Reframe headings as customer questions
Answer Readiness
high impactmedium effort- Why it matters
- Only six question-shaped headings were found across ten pages. A heading phrased as the question a customer would ask, answered immediately beneath it, is the most reliable pattern for producing a retrievable passage.
- Exact recommended change
- Convert descriptive subheadings on the service pages into the questions customers actually ask, then answer each in the two or three sentences directly below.
- Example implementation
<h2>How much does a roof replacement cost in Denver?</h2> <p>A standard asphalt shingle replacement on a 2,000 sq ft home in the Denver metro runs $9,500 to $16,000 as of 2026. Steeper pitches, tile and metal systems, and decking repairs increase that range.</p>
- Expected impact
- Closing this gap contributes a meaningful improvement to your Answer Readiness score (5.4 of 9 points currently unearned).
- 6
Replace vague claims with specific figures
Content Authority
high impactmedium effort- Why it matters
- Phrases like "industry-leading response times" carry no retrievable information. Specific figures give a model something concrete to quote.
- Exact recommended change
- Rewrite the eight vague phrases identified in the findings into measurable statements with real numbers.
- Example implementation
Replace "industry-leading response times" with "we respond to emergency calls within four business hours, and 92% of 2025 storm callouts were on site the same day."
- Expected impact
- Closing this gap contributes a modest improvement to your Content Authority score (3.5 of 7 points currently unearned).
Longer-term improvements2 actions
Investments that compound — original research, deep service pages and sustained publishing.
- 7
Deepen thin service pages
Content Authority
high impacthigh effort- Why it matters
- Service pages averaging 380 words rarely contain a passage long enough to answer a question on its own, so they are seldom cited even when they are relevant.
- Exact recommended change
- Expand each service page to cover what the service is, who it suits, the step-by-step process, realistic price ranges, typical timelines and what is included.
- Expected impact
- Closing this gap contributes a large improvement to your Content Authority score (4.1 of 9 points currently unearned).
- 8
Publish first-party evidence and case studies
Content Authority
high impacthigh effort- Why it matters
- Original data and detailed case studies are what distinguish a source worth citing from a page that restates common knowledge. None were found.
- Exact recommended change
- Publish at least six case studies structured as: the situation, what inspection found, what was done, what it cost, and the measured outcome — with dates and locations.
- Expected impact
- Closing this gap contributes a meaningful improvement to your Content Authority score (5.3 of 7 points currently unearned).
Page-by-page observations
| Page | Role | Status | Words | Schema | Q-headings |
|---|---|---|---|---|---|
| Denver Roofing Contractor | Atlas Roofing & Exteriorshttps://www.atlasroofingexteriors.example/Strong opening summary sentence; LocalBusiness schema present but incomplete. | home | 200 | 612 | RoofingContractor, WebSite | 2 |
| About Us | Atlas Roofing & Exteriorshttps://www.atlasroofingexteriors.example/aboutThin. Founding year present, no leadership, credentials or specialization. | about | 200 | 210 | none | 0 |
| Roof Replacement | Atlas Roofing & Exteriorshttps://www.atlasroofingexteriors.example/services/roof-replacementBest service page. Includes an FAQ block that is not marked up. | service | 200 | 548 | Service | 3 |
| Roof Inspection | Atlas Roofing & Exteriorshttps://www.atlasroofingexteriors.example/services/roof-inspectionNo pricing, process or timeline detail. | service | 200 | 301 | Service | 1 |
| Gutter Installation | Atlas Roofing & Exteriorshttps://www.atlasroofingexteriors.example/services/gutter-installationThinnest page on the site. No schema. | service | 200 | 212 | none | 0 |
| Siding | Atlas Roofing & Exteriorshttps://www.atlasroofingexteriors.example/services/sidingDuplicate opening paragraph shared with the gutter page. | service | 200 | 244 | none | 0 |
| Storm Damage Repair | Atlas Roofing & Exteriorshttps://www.atlasroofingexteriors.example/storm-damageContains an unmarked FAQ block and useful insurance-claim detail. | service | 200 | 497 | Service | 2 |
| Frequently Asked Questions | Atlas Roofing & Exteriorshttps://www.atlasroofingexteriors.example/faqNine real questions with good answers — no FAQPage schema. | faq | 200 | 734 | none | 9 |
| Contact | Atlas Roofing & Exteriorshttps://www.atlasroofingexteriors.example/contactFull NAP, hours and a map. Matches schema exactly. | contact | 200 | 186 | ContactPage | 0 |
| How to Prevent Ice Dams in Colorado | Atlas Roofinghttps://www.atlasroofingexteriors.example/blog/ice-dam-preventionStrongest content on the site, but published anonymously and undated. | article | 200 | 891 | BlogPosting | 4 |
Site-level files
- robots.txt
- Found
- XML sitemap
- Found (24 URLs)
- llms.txt
- Not found
- AI crawlers blocked
- None
Methodology
- Evidence collection
- A crawler identifying itself as RankInAI-Auditor fetches robots.txt, the XML sitemap and llms.txt, then requests up to your plan’s page limit of public HTML pages. It honors robots.txt rules for its own agent, follows a bounded number of redirects, enforces a response size cap and a request timeout, and never submits forms, signs in or executes downloaded files.
- Deterministic checks
- Roughly seventy checks run against the collected evidence. Each awards a fraction of its available points based on what was observed, and records the specific values it saw. Checks that cannot apply to a site are excluded from both the numerator and the denominator of its category score.
- Category scoring
- Each category score is round(100 × points awarded / points possible) across its applicable checks. Because the checks are pure functions of the collected evidence, the same website content always produces the same scores.
- Overall score
- The overall score is the weighted sum of the available category scores. Base weights are Technical Accessibility 15%, Entity Clarity 17%, Content Authority 18%, Answer Readiness 17%, Structured Data 13%, Trust and Evidence 15%, Competitive Visibility 5%. When a category is unavailable, its weight is redistributed proportionally across the rest.
- Prioritization
- Every failing or partial check becomes a recommendation, ordered by severity, then expected impact, then effort, then category. Recommendations are grouped into Do first, Next 30 days and Longer-term improvements.
- Optional AI enhancement
- When configured, a language model may rewrite summaries and explanations for clarity. It receives only already-computed scores and check outcomes, never raw page content, and can never change a score, a status or a recorded piece of evidence. Enhanced passages are labeled in the report.
Where each statement came from
- Observed — measured directly from your website during this audit. All scores derive from these.
- Public-web observation — what was publicly visible in search results at audit time. Never scored.
- AI-enhanced — wording improved by a language model working only from computed results. Never changes a score or evidence.
- Demo data — fictional information created for product demonstration. This entire report is demo data.
Limitations and disclaimer
- RankInAI measures signals that are publicly visible on your website at the time of the audit. It cannot see inside any AI system’s training data, retrieval index or ranking logic.
- No tool — including this one — can guarantee that ChatGPT, Perplexity, Gemini, Copilot or any other assistant will mention, cite or recommend a business.
- Scores describe AI visibility readiness: how well the site is set up to be discovered, understood, retrieved and attributed. They are not a prediction of traffic, referrals or revenue.
- The crawl is bounded by your plan and by what is publicly reachable. Content behind a login, a paywall, a form, or rendered only by client-side JavaScript after user interaction is not analyzed.
- Competitor analysis is based on a single public homepage fetch per competitor, not a full crawl. It compares homepage-level signals only.
- Public-web search observations, when present, describe publicly visible search results at the time of the audit. They are not evidence of behavior inside any particular AI product.
- Content and websites change. Re-run the audit after making changes to see the effect.