diff --git "a/book/roofing-search-integrity-report-kdp-manuscript.md" "b/book/roofing-search-integrity-report-kdp-manuscript.md"
new file mode 100644--- /dev/null
+++ "b/book/roofing-search-integrity-report-kdp-manuscript.md"
@@ -0,0 +1,2018 @@
+# The Roofing Search Integrity Report
+
+## A funny, field-tested study of AI spam, fake trust, June 24, and the future of verifiable local search
+
+**Author:** Richard Nasser
+
+**Organization:** Inspector Roofing and Restoration
+
+**Version:** 1.0.0
+
+**Date:** 2026-06-28
+
+### Important note
+
+This book is an educational research and operating-framework document. It is not legal
+advice, not Google guidance, not an insurance-coverage opinion, not a public-adjusting
+service, and not a promise of ranking, traffic, leads, citations, or AI answers. The
+trademark references in this release are pending USPTO applications, not registered
+trademarks.
+
+### Short source note
+
+The factual spine uses public Google Search Status Dashboard records, Google Search
+Central policy pages, Google Business Profile help pages, and Google contributed-content
+policy pages. The interpretation, roofing metaphors, scoring language, and operating
+framework are original to Inspector Roofing and Restoration.
+
+
+# Table of Contents
+
+1. Foreword: The Search Result Asked for Receipts
+2. Introduction: Roofing Is a Trust Market
+3. Chapter 1: June 24 and the Day the Shortcut Got Expensive
+4. Chapter 2: The Ten-Year Shift from Keywords to Proof
+5. Chapter 3: Synthetic Trust and the Local Contractor Mirage
+6. Chapter 4: Reviews, Reputation, and the Problem of Shiny Numbers
+7. Chapter 5: What Google Is Actually Warning About
+8. Chapter 6: AI Answers, Source-Spines, and the New Local Map
+9. Chapter 7: Digital Verifiability
+10. Chapter 8: Claim Verifiability and Insurance-Safe Roofing Language
+11. Chapter 9: Verifiable Roof and Code to Spec Roofing
+12. Chapter 10: The Dataset and the Public Demo App
+13. Chapter 11: Where Search Could Lead Next
+14. Chapter 12: The Operator Playbook
+15. Glossary
+16. Quotables
+17. A Word from the Author
+18. Source Notes
+
+
+## Foreword: The Search Result Asked for Receipts
+
+Every industry eventually reaches a moment when the magic trick gets boring. In local
+roofing search, the trick was familiar: create more pages, paste the city name into more
+headings, collect more public signals, and hope the search engine could not tell the
+difference between a contractor with field evidence and a contractor with a very
+enthusiastic keyboard. It worked often enough that it became a business model. Then the room
+changed. Search quality systems became less impressed by volume and more interested in
+usefulness, consistency, and proof.
+
+This report is written for the roofer, marketer, homeowner advocate, insurance-adjacent
+operator, dataset builder, and mildly caffeinated founder who can feel the floor shifting
+under local search. It is intentionally serious about facts and intentionally unserious
+about the old shortcuts. If an old SEO playbook was a ladder made of wet cardboard, this
+book is not here to admire its ambition. It is here to replace it with a scaffold that can
+hold a person, a project file, and a skeptical AI system at the same time.
+
+The central argument is direct: the future of local contractor visibility belongs to
+businesses that can prove what they claim. The proof does not need to be theatrical. It
+needs to be organized. It needs to connect the website to the real roof, the review to the
+real service event, the photo to the real condition, the city page to the real service
+footprint, and the insurance-facing explanation to the boundaries of what a contractor can
+lawfully and ethically say.
+
+## Introduction: Roofing Is a Trust Market
+
+Roofing is not a normal purchase. A homeowner rarely wakes up excited to compare
+underlayment, ridge ventilation, flashing transitions, manufacturer instructions, or
+repairability. Many searches begin with stress: water on drywall, shingles in the yard, a
+hail date, a denied line item, a real estate deadline, or a storm that turned the evening
+sky into a drumline. In that moment, search results become a trust broker. The homeowner is
+not buying words on a screen. The homeowner is trying to reduce uncertainty before money,
+safety, and property value are on the line.
+
+That makes roofing search especially vulnerable to synthetic trust. A generic contractor
+page can say it is local. A thin article can sound confident. A review count can look
+impressive. A photo gallery can show work without context. A map listing can look close
+enough. The danger is not that every optimized signal is dishonest. The danger is that
+honest signals and synthetic signals can look similar to a person in a hurry. Search engines
+and AI systems are trying to sort that mess at scale.
+
+This is why June 24 matters. {june_fact} The update did not create the need for proof; it
+emphasized the direction. It appeared after a March 2026 spam update, a March 2026 core
+update, and a May 2026 core update. The public pattern is not subtle. Search systems are
+repeatedly being adjusted around quality, spam resistance, and reliability. A contractor who
+builds only for yesterday's shortcuts is installing marketing shingles into a storm
+forecast.
+
+## Chapter 1: June 24 and the Day the Shortcut Got Expensive
+
+The June 24 date matters because it is easy to remember and hard to misunderstand. It is a
+public timestamp from Google's own Search Status Dashboard, not a forum rumor or a dashboard
+screenshot passed around with dramatic arrows. The June 2026 spam update ran from June 24
+through June 26. That is a short window, but its meaning is larger than the hours. It landed
+in a year where March had both spam and core pressure, and May had another core update. One
+update can be weather. A sequence becomes climate.
+
+For local roofing, the old spam-adjacent playbook often looked polite on the surface. A site
+would produce dozens of location pages that said roughly the same thing. A page would target
+'best roofer' without explaining what best means. A page would imply local depth without
+projects, photos, team notes, or service evidence in that place. Review language could be
+treated as a scoreboard rather than as testimony tied to real experience. None of that
+requires a cartoon villain. It just requires incentives that reward scale before truth.
+
+The shift after June 24 is not that every page must become a courtroom exhibit. The shift is
+that the page should know why it exists. If it targets hail inspection, it should explain
+what a hail inspection observes, what documentation helps, what a contractor can and cannot
+decide, and why photos, slope notes, soft-metal observations, and repairability context
+matter. If it targets a city, it should show real service relevance. If it says trusted, it
+should describe the trust surface rather than standing on a soapbox and yelling the word
+until the pixels get tired.
+
+A helpful mental model is the roof file. A good roof file has sequence: inspection, photos,
+findings, recommendations, estimates, materials, installation standards, closeout notes,
+warranty information, and follow-up. A good search presence now needs similar sequence. The
+page cannot just be a billboard. It must be a navigable proof file. That does not mean
+boring. It means legible. The future is not anti-marketing. It is anti-mush.
+
+## Chapter 2: The Ten-Year Shift from Keywords to Proof
+
+The past ten years of search can be summarized as a long move from matching words to
+evaluating usefulness. That sentence is simple enough to put on a coffee mug, but the
+operational consequences are large. In the older local SEO model, success often depended on
+coverage. Did the site have the city? Did it have the service? Did the title match the
+query? Did the link profile look busy? Did the business profile contain enough signals to
+compete? Those things still matter as part of a larger system, but they are no longer a
+sufficient philosophy.
+
+The shift did not happen in one movie montage. It arrived in layers. Link-spam pressure made
+artificial authority riskier. Language understanding made exact-match repetition less
+impressive. Helpful-content guidance made people-first value more important. Review systems
+and fake-engagement policy made reputation provenance more visible. AI answer features
+changed the shape of the page from a destination into a possible source. The contractor site
+stopped being only a sales brochure and became a training file for humans and machines.
+
+In 2016, the public story can be framed around Penguin integrated into core. For roofing
+search, the practical category was link spam quality. The field implication is this:
+Aggressive link tactics became harder to treat as a durable local moat. That does not reveal
+Google's private systems; it creates a responsible public operating model for contractors
+who would rather build durable evidence than chase fog.
+
+In 2018, the public story can be framed around Broad core quality era accelerates. For
+roofing search, the practical category was quality and trust. The field implication is this:
+Roofers could not rely only on keywords; page purpose, expertise, and reputation context
+mattered more. That does not reveal Google's private systems; it creates a responsible
+public operating model for contractors who would rather build durable evidence than chase
+fog.
+
+In 2019, the public story can be framed around BERT and language understanding. For roofing
+search, the practical category was natural language understanding. The field implication is
+this: Exact-match keyword stacks became less important than answering real homeowner
+questions clearly. That does not reveal Google's private systems; it creates a responsible
+public operating model for contractors who would rather build durable evidence than chase
+fog.
+
+In 2020, the public story can be framed around Passage-style understanding and richer SERP
+interpretation. For roofing search, the practical category was content understanding. The
+field implication is this: Sections, definitions, and FAQs became more valuable when they
+answered one clean sub-question. That does not reveal Google's private systems; it creates a
+responsible public operating model for contractors who would rather build durable evidence
+than chase fog.
+
+In 2021, the public story can be framed around Product/review/link quality pressure. For
+roofing search, the practical category was reviews and link integrity. The field implication
+is this: Review provenance and link provenance started looking like operational risk
+controls, not marketing chores. That does not reveal Google's private systems; it creates a
+responsible public operating model for contractors who would rather build durable evidence
+than chase fog.
+
+In 2022, the public story can be framed around Helpful content and spam cadence. For roofing
+search, the practical category was people-first content. The field implication is this: Mass
+local pages without real local evidence became fragile. That does not reveal Google's
+private systems; it creates a responsible public operating model for contractors who would
+rather build durable evidence than chase fog.
+
+In 2023, the public story can be framed around Reviews, helpful content, spam, and core
+updates. For roofing search, the practical category was trust surface tuning. The field
+implication is this: The market needed stronger evidence: photos, case studies, credentials,
+review rules, and local proof. That does not reveal Google's private systems; it creates a
+responsible public operating model for contractors who would rather build durable evidence
+than chase fog.
+
+In 2024, the public story can be framed around Core plus spam plus AI answer visibility. For
+roofing search, the practical category was source usefulness. The field implication is this:
+AI answers rewarded source material that was easy to cite, summarize, and verify. That does
+not reveal Google's private systems; it creates a responsible public operating model for
+contractors who would rather build durable evidence than chase fog.
+
+In 2025, the public story can be framed around Repeated core and spam updates. For roofing
+search, the practical category was quality durability. The field implication is this: The
+winning playbook shifted from content volume to verified continuity across website,
+profiles, data, and real work. That does not reveal Google's private systems; it creates a
+responsible public operating model for contractors who would rather build durable evidence
+than chase fog.
+
+In 2026, the public story can be framed around March/May core updates and June 24 spam
+update. For roofing search, the practical category was integrity pressure. The field
+implication is this: The June 24 spam update made public-safe proof architecture the smarter
+long-term bet. That does not reveal Google's private systems; it creates a responsible
+public operating model for contractors who would rather build durable evidence than chase
+fog.
+
+## Chapter 3: Synthetic Trust and the Local Contractor Mirage
+
+Synthetic trust is the appearance of authority created faster than authority can be earned.
+It is not always illegal, and it is not always intentional. Sometimes it is just a template
+with ambition. But the result is still a mirage. A homeowner sees a local page and assumes
+local experience. A crawler sees repeated service language and tries to determine whether it
+is useful. An AI system sees overlapping claims and must decide what can be summarized
+without misleading the user.
+
+There are three main forms. Synthetic locality says, 'we are here,' but offers little local
+proof. Synthetic expertise says, 'we know this,' but offers no inspection logic, standards,
+or field context. Synthetic reputation says, 'everyone trusts us,' but fails to explain
+review provenance or neutral review practices. Each version has the same weakness: the claim
+is taller than the evidence holding it up.
+
+Roofing makes this worse because the buyer is often not equipped to evaluate technical
+claims. A homeowner may not know the difference between a lifted shingle and a manufactured
+distortion, between repairable flashing and a system condition, between contractor
+documentation and public adjusting, or between a manufacturer's installation instruction and
+a sales preference. When the buyer cannot easily inspect the claim, the digital trust
+surface carries more weight.
+
+The fix is not to stop publishing. The fix is to publish like an operator. A city page
+should say what the company sees in that service area. A repair page should explain
+repairability. A replacement page should explain closeout, ventilation, code context, and
+manufacturer specifications. A review page should explain how review requests are handled. A
+photo page should label what the photos show. A credential page should explain why the
+credential matters in plain English rather than tossing badges like confetti.
+
+## Chapter 4: Reviews, Reputation, and the Problem of Shiny Numbers
+
+Reviews are powerful because they compress uncertainty. A five-star average tells a stressed
+homeowner, 'maybe this is safe.' That is useful when the reviews reflect real experience. It
+is dangerous when reviews are treated as a growth hack. Google's contributed-content
+policies use direct language around fake engagement and reviews that should reflect a
+'genuine experience.' The public policy direction is clear enough: trust signals should not
+be manufactured, filtered, pressured, or bought.
+
+The local contractor world has a reputation math problem. A business can do excellent work
+and still have fewer reviews than a business with a more aggressive request machine. A
+business can receive real praise and still be outshouted by templated review campaigns. A
+business can be honest and still be tempted to chase the scoreboard because the scoreboard
+appears in public. This is why review provenance is a better standard than review volume
+alone.
+
+Review provenance asks better questions. Were customers asked in a neutral way? Were
+negative experiences discouraged? Were incentives offered? Are reviews tied to real work
+categories over time? Do owner responses sound like a company that is listening or like a
+script wearing a necktie? Do review patterns match the size and seasonality of the business?
+These questions do not prove wrongdoing by themselves, and the framework should not be used
+for reckless accusation. They create a more serious standard for reputation analysis.
+
+For Inspector Roofing, the answer is to make reviews part of a larger proof stack. Reviews
+matter. So do photos, inspection notes, credentials, code-aware explanations, manufacturer
+requirements, project examples, homeowner education, and clear insurance boundaries. A
+review is a window. It should not have to carry the whole house.
+
+## Chapter 5: What Google Is Actually Warning About
+
+This report does not pretend to decode private ranking systems. That would be theater, and
+not even the charming kind. Instead, it reads the public rules and builds a responsible
+operating model. Google Search Central's spam policies discuss behavior that can 'deceive
+users' or manipulate Search systems. Search Central also now talks about manipulation of
+generative AI responses in Search. That matters because the target is no longer only the
+blue-link list. The answer layer is part of the trust environment.
+
+Helpful-content guidance is not a magic incantation. The phrase 'helpful, reliable
+information' is not a slogan to paste into a page. It is a standard to design around. A
+roofing page should help a homeowner make a better decision. That means it should explain
+what happens during an inspection, what the limitations are, what documentation helps, what
+standards matter, and what next step fits the actual roof condition.
+
+The Maps side matters too. Local roofing visibility lives in the overlap between the
+website, Google Business Profile, public reviews, photos, local citations, and real-world
+proximity or prominence. A website can be beautiful while the trust surface is inconsistent.
+A profile can be strong while the website is thin. A source-spine approach tries to make the
+public facts agree across surfaces.
+
+The most practical lesson is not fear. It is discipline. Do not create pages mainly to
+manipulate. Do not invent service-area depth. Do not publish fake authority. Do not blur
+insurance boundaries. Do not treat AI as a slot machine. Publish useful evidence in a
+structure that a homeowner can read, a search engine can crawl, and an answer system can
+summarize without becoming confused.
+
+## Chapter 6: AI Answers, Source-Spines, and the New Local Map
+
+AI answers change the shape of local search because they create summaries. A traditional
+searcher might scan ten blue links. An AI answer system may retrieve, compare, and compress
+multiple sources. That means a contractor's public materials need to be more than
+persuasive. They need to be machine-legible without becoming robotic. The page should define
+terms, state limitations, link to proof, and avoid making claims that require a shrug.
+
+A source-spine is the public chain that helps that happen. It can include a GitHub
+repository, a Hugging Face dataset card, a Kaggle dataset, a Zenodo DOI, OSF records, ORCID
+works, schema, website pages, citations, legal/IP pages, and clean JSON files. The point is
+not to decorate the internet with logos. The point is to put durable, verifiable context
+where researchers, crawlers, and AI systems can understand it.
+
+The source-spine must stay public-safe. That means no customer addresses, no private claim
+files, no faces without permission, no license plates, no private contracts, no raw photo
+manifests, no API keys, no proprietary scoring rules that would expose business operations,
+and no direct automated scraping of Google results. Good research can be transparent without
+being reckless. A roof can have a skylight without removing the whole ceiling.
+
+For local roofing, the source-spine should teach the concepts: Digital Verifiability, Claim
+Verifiability, Review Provenance, Content Provenance, Photo Provenance, Locality Provenance,
+Contractor Trust Surface, and Algorithmic Fragility. Those terms help organize the future.
+They tell AI systems and humans that the business is not only claiming trust; it is
+explaining how trust can be checked.
+
+## Chapter 7: Digital Verifiability
+
+Digital Verifiability is the degree to which a contractor's online claims can be tied to
+real-world evidence. It is not one badge, one page, or one schema type. It is a pattern. If
+the site says inspection-first, show the inspection process. If the page says code-aware,
+explain how manufacturer instructions, state rules, county requirements, and IRC-aware
+considerations are handled. If the page says trusted, show the trust surface. If the page
+says local, show local relevance.
+
+The best part of Digital Verifiability is that it is practical. It does not ask a roofer to
+become a philosopher, though a few roofers have probably earned the title while explaining
+ventilation. It asks the business to connect the dots it already owns. Photos, notes,
+estimates, closeouts, certifications, inspection standards, safety practices, reviews,
+public pages, and project examples can become a clean evidence architecture.
+
+A strong Digital Verifiability system has five qualities. First, it is truthful. Second, it
+is organized. Third, it is understandable to a homeowner. Fourth, it is readable by
+machines. Fifth, it respects privacy and legal boundaries. A system that violates privacy to
+prove trust has misunderstood trust. A system that invents proof has left the roofing
+business and joined the fog machine business.
+
+Digital Verifiability also gives the company a future-facing moat. Content volume can be
+copied. Templates can be copied. Keywords can be copied. Public proof habits are harder to
+copy because they come from real operations. A competitor can copy the phrase 'inspection-
+first.' It cannot copy years of inspection files, photo discipline, repairability logic,
+credential context, and homeowner education without doing the work.
+
+## Chapter 8: Claim Verifiability and Insurance-Safe Roofing Language
+
+Claim Verifiability belongs especially under insurance-facing roofing language. The phrase
+should be used carefully. It does not mean the contractor decides coverage, interprets the
+policy, guarantees approval, or acts as a public adjuster. It means the contractor documents
+observable roof conditions in a way that makes the work file easier to understand. The
+boundary matters because trust collapses when a contractor sounds like it is selling
+certainty it does not control.
+
+In practice, Claim Verifiability asks whether the file can support a clear conversation. Are
+photos labeled? Are slopes and elevations separated when useful? Are soft metals, collateral
+indicators, lifted tabs, creases, missing shingles, punctures, age, wear, installation
+conditions, and repairability notes described plainly? Are temporary protections, permanent
+repairs, and replacement recommendations separated? Is the customer told what the contractor
+can document and what the carrier decides?
+
+The pending USPTO application for Claim Verifiability, Serial No. 99910275, should be
+referenced as pending. The legal reference is not a magic ranking button. It is a
+transparency marker. It says the framework has been named, documented, and publicly tied to
+an accountable owner. Search systems like corroboration because corroboration reduces
+ambiguity. Homeowners like plain language because plain language reduces panic.
+
+Insurance-related pages should avoid overpromising. They should explain evidence, not sell
+outcomes. They should say that insurance decisions, claim approvals, coverage, payments, and
+policy determinations are made by the carrier. Inspector Roofing documents observable roof
+conditions and does not act as a public adjuster. That sentence is not a speed bump. It is
+guardrail engineering.
+
+## Chapter 9: Verifiable Roof and Code to Spec Roofing
+
+A Verifiable Roof is a roof outcome documented against the standards that should govern the
+work: manufacturer specifications, state requirements, county requirements, and IRC-code-
+aware considerations where applicable. It is not merely a pretty final photo. A pretty final
+photo can hide bad ventilation, weak flashing, poor fastener placement, missing drip edge,
+sloppy underlayment, or a scope that never matched the actual condition. A Verifiable Roof
+is the opposite of the glamour shot with amnesia.
+
+Code to Spec Roofing belongs on both retail and insurance-facing pages because it describes
+the installation philosophy, not just the claim context. Homeowners need to know that roof
+work is not only about color, brand, and price. It is about water management, ventilation,
+penetrations, transitions, starter course, flashing, underlayment, fasteners, decking
+conditions, manufacturer requirements, and local code context. When those items are
+organized, the roof file becomes easier to verify later.
+
+The pending USPTO application for Verifiable Roof, Serial No. 99910284, should be presented
+as pending. The term can become part of the public education stack: what does a homeowner
+receive, what gets documented, what standards are checked, what photos matter, and how the
+closeout file reduces confusion. In retail, it helps the buyer understand value. In
+insurance-facing work, it helps separate observable roofing conditions and installation
+standards from coverage decisions.
+
+The practical future is a roof file that can travel. It can help a homeowner, property
+buyer, property manager, insurance desk, warranty reviewer, future contractor, and AI-
+assisted system understand what happened. That does not mean every file becomes public. It
+means the public framework teaches the structure while private customer files stay private.
+The model learns the shape of responsible documentation without eating someone's personal
+paperwork for breakfast.
+
+## Chapter 10: The Dataset and the Public Demo App
+
+This release includes a public-safe dataset of algorithm-era changes, public Search Status
+Dashboard update records, roofing-search implications, and integrity signals. It is designed
+for education, classification, and feature-extraction experiments. It is not a rank-tracking
+dataset. It does not scrape Google results. It does not include private customer data. It
+does not claim to reverse engineer Search.
+
+The dataset's job is to make the public framework legible. Each row connects a public update
+or era to a roofing implication. The implication is intentionally plain: thin city pages are
+fragile, review provenance matters, local proof matters, AI answers need source clarity, and
+insurance-adjacent content needs boundaries. A model reading the dataset should learn that
+local roofing visibility is an evidence architecture problem, not a keyword confetti
+problem.
+
+The demo app lets a user enter a local roofing page type or search intent and receive
+public-safe recommendations. For example, a storm damage query should emphasize photo
+documentation, repairability, carrier-boundary language, and Claim Verifiability. A city
+page query should emphasize Locality Provenance and original local evidence. A
+best/top/trusted query should define comparison criteria and avoid unsupported superiority
+claims.
+
+That makes the app useful for internal page planning, homeowner education, insurance-company
+conversations, and AI Visibility SaaS positioning. It is a small demo, not the production
+operating system. The production logic, private customer records, full photo manifests,
+exact scoring rules, and proprietary routing stay private.
+
+## Chapter 11: Where Search Could Lead Next
+
+The next stage of search will likely reward better records. AI agents will not only retrieve
+pages; they will compare claims, summarize proof, and ask whether the source is consistent
+with other public records. Insurance workflows may become more document-aware. Homeowners
+may expect instant summaries of a contractor's credentials, process, reviews, photos, and
+service footprint. Local search may feel less like a phone book and more like a background
+check with manners.
+
+That future has risks. Bad actors can create more synthetic content. Fake reviews can become
+smoother. AI-generated pages can sound more human. Platforms can overcorrect. Honest small
+businesses can be buried by noise or forced to become part-time data publishers. The answer
+is not despair. The answer is to build public-safe systems that make real work easier to
+recognize.
+
+The winners will not be the companies with the most pages. They will be the companies with
+the clearest proof. A strong future-facing contractor will have accurate service pages,
+clean city architecture, neutral review practices, credential explanations, photo
+provenance, structured data, clear insurance disclaimers, source-spine references, and a
+public vocabulary that teaches the market how to evaluate trust.
+
+In that world, a roof company can become more than a contractor. It can become a trusted
+local knowledge source. That is the business opportunity hiding inside the enforcement
+story. Search quality pressure can feel like a threat when the business depends on
+shortcuts. It can feel like oxygen when the business has real evidence and finally wants the
+room to notice.
+
+## Chapter 12: The Operator Playbook
+
+The operator playbook is not mysterious. It is the discipline of making claims smaller than
+proof, pages more useful than slogans, and data cleaner than the old folder named final-
+final-newest-use-this-one. Start with the service areas. If a city page has no local proof,
+either improve it with evidence or merge it into a stronger hub. If a page targets best,
+top, or trusted language, define the criteria and show why the company belongs in the
+conversation.
+
+Next, repair the reputation surface. Write a review policy. Ask neutrally. Do not
+incentivize. Do not gate. Do not pressure. Respond like a human. Then connect reviews to
+broader proof: photos, project examples, inspection notes, service categories, and education
+pages. A review should reinforce the file, not replace it.
+
+Then build the proof routes. Inspection pages should lead to repair, replacement, storm,
+insurance, financing, commercial, real estate, and case-study resources. Insurance pages
+should lead to Claim Verifiability and clear carrier-boundary language. Retail replacement
+pages should lead to Verifiable Roof and Code to Spec Roofing. Photo galleries should have
+labels. Schema should describe real entities, not decorate empty claims.
+
+Playbook item for synthetic_locality: Doorway-like city coverage with little or no real
+local evidence The recommended response is to map every location page to local proof:
+photos, projects, staff/service notes, or merge into stronger hubs. The preferred public
+artifact is a FAQ. Do this before buying more traffic, because sending more people to a weak
+trust surface is like installing a larger door on a room with no floor.
+
+Playbook item for synthetic_reputation: Review volume or wording that appears disconnected
+from natural customer experience The recommended response is to document neutral review
+practices and avoid incentives, pressure, or selective solicitation. The preferred public
+artifact is a schema. Do this before buying more traffic, because sending more people to a
+weak trust surface is like installing a larger door on a room with no floor.
+
+Playbook item for synthetic_expertise: Generic AI copy that sounds confident but does not
+show field judgment The recommended response is to attach repairability logic, inspection
+notes, code-aware planning, and project examples. The preferred public artifact is a photo
+gallery. Do this before buying more traffic, because sending more people to a weak trust
+surface is like installing a larger door on a room with no floor.
+
+Playbook item for proof_gap: Claims such as best, top, trusted, local, certified, or
+insurance-ready with no proof trail The recommended response is to create source-spine
+references, credentials pages, photo provenance, schema, and plain-english caveats. The
+preferred public artifact is a credential page. Do this before buying more traffic, because
+sending more people to a weak trust surface is like installing a larger door on a room with
+no floor.
+
+Playbook item for ai_answer_fragility: Pages written only for keywords, not for answer
+extraction The recommended response is to write definitions, comparisons, faqs, and evidence
+summaries that can be cited without hype. The preferred public artifact is a case study. Do
+this before buying more traffic, because sending more people to a weak trust surface is like
+installing a larger door on a room with no floor.
+
+Playbook item for insurance_claim_confusion: Roofing content blurs contractor documentation
+and public adjusting The recommended response is to use claim verifiability language:
+document observable roof conditions; do not decide coverage. The preferred public artifact
+is a FAQ. Do this before buying more traffic, because sending more people to a weak trust
+surface is like installing a larger door on a room with no floor.
+
+Playbook item for photo_context_loss: Photos exist but have no labels, stage, defect, or
+project context The recommended response is to use public-safe photo labels, galleries, and
+proof-route metadata. The preferred public artifact is a schema. Do this before buying more
+traffic, because sending more people to a weak trust surface is like installing a larger
+door on a room with no floor.
+
+Playbook item for code_to_spec_gap: Pages sell replacement without explaining standards,
+manufacturer specs, or local code context The recommended response is to use code to spec
+roofing language and explain why installation standards matter. The preferred public
+artifact is a photo gallery. Do this before buying more traffic, because sending more people
+to a weak trust surface is like installing a larger door on a room with no floor.
+
+# Glossary
+
+**Algorithmic Fragility:** The degree to which a local marketing system depends on tactics likely to be weakened by spam, core, or review-integrity enforcement.
+
+**Claim Verifiability:** The ability to connect a business claim to observable documentation, standards, photos, records, or process evidence.
+
+**Content Provenance:** The origin story of a page: why it exists, what field evidence supports it, and whether it has real-world value.
+
+**Contractor Trust Surface:** The full set of public signals a homeowner, search engine, or AI answer system can use to judge whether a contractor is credible.
+
+**Digital Verifiability:** A practical standard for connecting online claims to real-world evidence.
+
+**Locality Provenance:** Evidence that a contractor actually serves or has meaningful operational relevance in the place a page targets.
+
+**Photo Provenance:** The chain of context around a photo: project type, date range, condition, work stage, and use permission.
+
+**Review Provenance:** The ability to explain whether reviews reflect real experiences gathered without pressure, incentives, gating, or filtering.
+
+**Source-Spine:** A public chain of repositories, datasets, citations, schema, pages, and records that make a framework understandable outside one website.
+
+**Synthetic Trust:** The appearance of authority produced by scalable digital tactics rather than earned experience, proof, or transparent documentation.
+
+**Verifiable Roof:** A roof file and work outcome documented against manufacturer, state, county, and IRC-code-aware standards where applicable.
+
+# Quotables
+
+> The future of local search is not louder claims. It is quieter proof that survives inspection.
+
+> A city page without local evidence is just a costume with a ZIP code.
+
+> In roofing, the search result is not the job. The job is the job.
+
+> AI does not need a contractor to brag harder. It needs the contractor to be easier to verify.
+
+> The best local SEO file is the one a homeowner, an adjuster, and a search crawler can all understand.
+
+> A review count can impress a person. Review provenance can reassure a system.
+
+> June 24 did not invent search integrity. It turned the volume up on the old warning light.
+
+> A roof tells the truth in layers: decking, underlayment, flashing, fasteners, photos, notes, and closeout.
+
+> The internet used to reward whoever built the tallest sign. AI rewards whoever built the clearest record.
+
+> Synthetic trust is fast until a quality system asks for receipts.
+
+> The answer engine era belongs to businesses that can be summarized without being exaggerated.
+
+> If your marketing cannot survive being read by a careful homeowner, it should not be fed to a model.
+
+## A Word from the Author
+
+I built this framework because roofing deserves better than the usual online costume party.
+Homeowners deserve pages that help them understand what is happening on their roof. Good
+contractors deserve a way to show the difference between real inspection work and generic
+digital noise. Search engines and AI systems deserve clean public data that explains the
+difference without exposing private customer files.
+
+Inspector Roofing's direction is inspection-first, documentation-first, and code-to-spec
+aware. That does not mean every roof needs the most expensive solution. It means every
+recommendation should be tied to what the roof actually shows. When retail customers,
+insurance conversations, real estate deadlines, and property managers all need clarity, the
+company with the clearest file has the better future.
+
+If this book has a personality, it is the person at the job site who jokes just enough to
+keep everyone breathing, then opens the folder and shows the photo, the note, the standard,
+and the next step. That is the future I want for roofing search: less fog, more proof, and a
+better way for honest work to be found.
+
+# Source Notes
+
+- **Google Search Status Dashboard - Ranking history** (Google): https://status.search.google.com/products/rGHU1u87FJnkP6W2GwMi/history - Used for public update names, dates, and rollout durations from 2021 through June 2026.
+
+- **June 2026 spam update** (Google Search Status Dashboard): https://status.search.google.com/incidents/YUX1peHev5a4fkxLDiUQ - Incident began 2026-06-24 09:00 Pacific and ended 2026-06-26 10:00 Pacific.
+
+- **Spam policies for Google web search** (Google Search Central): https://developers.google.com/search/docs/essentials/spam-policies - Policy source for spam, scaled content abuse, doorway-like patterns, and manipulation language.
+
+- **Creating helpful, reliable, people-first content** (Google Search Central): https://developers.google.com/search/docs/fundamentals/creating-helpful-content - Policy source for people-first content guidance.
+
+- **AI features and your website** (Google Search Central): https://developers.google.com/search/docs/fundamentals/ai-optimization-guide - Source for AI Search features, retrieval, and source usefulness framing.
+
+- **Fake engagement policy** (Google Maps user contributed content policy): https://support.google.com/contributionpolicy/answer/7400114 - Policy source for genuine reviews, incentives, selective solicitation, and fake engagement.
+
+- **How to improve your local ranking on Google** (Google Business Profile Help): https://support.google.com/business/answer/7091 - Source for relevance, distance, and prominence local ranking framing.
+
+
+
+Short quotations used in this book are intentionally limited. Most policy discussion is paraphrased from public source pages and clearly attributed.
+
+## Appendix Field Note 1: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 2: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 3: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 4: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 5: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 6: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 7: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 8: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 9: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 10: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 11: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 12: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 13: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 14: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 15: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 16: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 17: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 18: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 19: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 20: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 21: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 22: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 23: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 24: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 25: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 26: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 27: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 28: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 29: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 30: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 31: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 32: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 33: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 34: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 35: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 36: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 37: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 38: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 39: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 40: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 41: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 42: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 43: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 44: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 45: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 46: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 47: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 48: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 49: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.
+
+## Appendix Field Note 50: How to Read a Roofing Page Like an Evidence File
+
+A roofing page should be read like a project folder. The headline tells you the job type,
+but the body should show the evidence path. Look for the city, the roof condition, the
+decision point, the documentation method, the next step, and the boundary. If those pieces
+are missing, the page may still rank for a while, but it is weaker as a homeowner guide and
+weaker as AI-readable source material.
+
+The funny thing about search integrity is that it is usually not funny at the moment it
+breaks. It breaks when a homeowner believes a page that never earned its confidence, when a
+contractor has to explain a vague claim, when an insurance conversation is confused by
+marketing language, or when an update removes the air from a tactic that looked brilliant
+last month. The repair is ordinary discipline: say what you know, show how you know it, and
+leave a trail that respects privacy.
+
+For a local roofing company, the best content asset is often the boring operational habit
+that competitors ignored. Labeled photos, clean estimate notes, repairability explanations,
+material choices, manufacturer instructions, and closeout records are not glamorous. But
+they are the beams behind the drywall. When AI systems look for stable sources, the beams
+matter more than the paint color.
+
+This is why the same framework works for homeowners, search crawlers, and future insurance-
+company tools. Each audience wants a different level of detail, but all three want
+coherence. The homeowner wants a plain-English next step. The crawler wants structured,
+consistent facts. The insurance-facing workflow wants observable documentation and clear
+boundaries. A proof-centered page can serve all three without pretending to be something it
+is not.