1. Name the issue
Say what the page is about in plain terms. Avoid cute headlines when the homeowner is trying to make a practical decision.
Content Rules
Answer the question up top. Earn the deeper scroll.
Raptor content should feel useful before it feels promotional. The homeowner should understand the issue, the options, the likely next step, and why Raptor is a trustworthy guide before the page asks for more attention.
Answer-first rule
The first screen should reduce uncertainty.
A homeowner may arrive worried about a leak, comparing materials, checking a contractor, or trying to understand a storm issue. Raptor should meet that moment with direct guidance.
2. Give the short answer
Explain what the service, material, or topic means and what Raptor can help determine during an inspection.
3. Show the next step
Use Book A Free Inspection, Call, View Services, or Read Reviews. The action should match the page intent.
Question map
Every major page should answer these questions in order.
These questions are the content backbone. The exact wording changes by page type, but the order should remain consistent enough that any homeowner can follow the page.
Above the fold and early page
- What is this page about?
- Is this something I might need?
- What does Raptor inspect, repair, replace, or explain?
- What is the safest next step?
- Why should I trust Raptor with this decision?
Middle and lower page
- What are the common options or materials?
- How does the process work?
- What can affect cost, timing, or project scope?
- What local weather or home-style context matters?
- What related service or guide should I read next?
Depth model
The page should feel light at the top and substantial at the bottom.
A strong Raptor page has a fast answer for the homeowner who wants help now and a deeper learning path for the homeowner who wants to compare, plan, and understand the work.
- Top sections should be concise, decision-focused, and action-ready.
- Middle sections should build confidence with process, proof, and common concerns.
- Lower sections should teach through FAQs, comparisons, material guidance, and related content.
- The lead form should appear after value has been delivered, not as an interruption.
Fast Answer
What it is, whether it matters, and how Raptor can help.
Deep Guide
Materials, method, fit, proof, local context, FAQs, and related pages.
Voice rules
Useful, specific, and steady beats loud, vague, and sales-heavy.
Raptor should sound like a confident local operator, not a national call center. Every sentence should help the homeowner understand the decision or trust the process.
Write for the homeowner's moment.
- Storm pages should be calm and organized.
- Premium material pages should explain fit and tradeoffs.
- Team pages should make people and roles feel real.
- Contact pages should reduce friction.
Use specifics that prove experience.
- Decking, flashing, ventilation, cleanup, and walkthroughs.
- Gutters, siding, windows, insulation, and roof system connections.
- Indianapolis, Carmel, Greenwood, Fishers, Noblesville, Avon, and nearby communities.
- Wind, hail, freeze-thaw cycles, drainage, and attic comfort.
Remove language that weakens trust.
- No filler intros that delay the answer.
- No scare tactics or pressure language.
- No unsupported superlatives.
- No generic copy that could fit any contractor.
Reusable modules
Use modules that make the page easier to scan.
Raptor pages should be structured, not wall-of-text. These modules create a repeatable rhythm for designers and writers.
Quick Takeaway
A short panel near the top that gives the practical answer in plain language.
Common Signs
A scan-friendly list that helps homeowners recognize whether the issue applies to them.
What Raptor Checks
A process-based list showing what the team will inspect, document, and explain.
Fit Guide
Who this option is for, who it is not for, and what tradeoffs matter.
Comparison Block
Material or service comparisons written honestly without pushing one answer for every home.
Project Proof
Real photos, team references, before-and-after context, and local project notes.
FAQ Cluster
Direct answers to the questions a homeowner asks before calling.
Next Step Panel
A clear inspection, call, or service exploration path that matches the page topic.
Claim safety
Some language belongs in Proof Review before it becomes standard.
Raptor Brand Kit can spot when brand review is not enough. Any claim that could affect trust, pricing, credentials, performance, or customer expectation should be routed for verified approval.
Usually fine in Raptor Brand Kit
- Clear descriptions of the service process.
- General local service-area language.
- Plain-language explanations of materials and options.
- Internal tone, imagery, CTA, and layout review.
Needs careful review
- Review counts, star ratings, awards, and badges.
- Same-day, fastest, best, or highest-rated language.
- Financing, warranty, or manufacturer credential language.
- Pricing, savings, or timeline expectations.
Needs Proof Review
- Guaranteed results or guaranteed claim outcomes.
- Legal, insurance, or compliance-sensitive statements.
- Claims that require proof from a platform, manufacturer, or internal record.
- Anything that should become approved brand truth for future use.
Publishing checklist
No Raptor page should go live until it passes these checks.
This checklist keeps quality high even as more providers touch the website, social, ads, and content calendar.
Content checks
- The main homeowner question is answered in the first meaningful section.
- The CTA matches the page intent and uses approved language.
- The copy sounds specific to Raptor and Central Indiana.
- The deeper learning sections add real value, not filler.
- Claim-sensitive language has a Proof Review path.
Experience checks
- Mobile text fits and does not collide with images or buttons.
- Real images are crisp, properly cropped, and relevant.
- Buttons, cards, and page sections follow the Brand Kit.
- Related pages are linked where they help the homeowner continue.
- The page feels helpful before it feels promotional.