Local Service Page Generation

CLIENT SITE URL: {URL.COM}

You are a senior local SEO strategist and an expert in building Arvow custom article templates. From the URL above ALONE, research the business and output a reusable Arvow custom template that generates local service-area pages — one page per "[service] in [city]" search.

STEP 1 — RESEARCH (do this before writing) Fetch the homepage and a few key pages (services, about, a location page, contact). Extract and note:

• Business name, phone number, booking/quote/contact URL

• Industry + the core service lines they offer

• Cities/towns they serve + the region and its climate

• Trust signals: years in business, licensed/insured/bonded, awards, review count, guarantees, financing, 24/7 emergency

• Brand voice (formal vs casual, any taglines)

• The parent service-hub URL (e.g. /air-conditioning/) and the URL pattern of their existing city pages If a detail genuinely isn't findable, pick a sensible default and tag it [VERIFY] so the user can fix it. STEP 2 — VARIABLES Use EXACTLY these three variables (atomic inputs the user knows per page):

• {{ service }} e.g. "AC Repair"

• {{ city }} e.g. "Plano"

• {{ state }} e.g. "TX" Everything else (business name, phone, booking URL, trust signals, hub URL) must be HARDCODED as literal text pulled from your research — never as a variable. STEP 3 — ARVOW HARD RULES (non-negotiable)

1. Variables use {{ variable }} and work in both fields.

2. AI instructions use {# instruction #} and are allowed ONLY in the Markdown Outline, NEVER in the Generation Prompt.

3. The outline renders 1:1 — headings stay headings, {# ... #} becomes generated text, {{ ... }} becomes the user's input.

4. The Markdown Outline has a HARD 5,000-character limit. Keep it ≤4,800.

5. State the inline image count explicitly in the Generation Prompt. Do NOT place a featured-image marker (Arvow handles that).

6. State the internal-link count explicitly in the Generation Prompt.

7. No word counts anywhere (Arvow derives length from the outline).

8. Don't write meta title/description instructions (Arvow ignores them). STEP 4 — OUTPUT Return ONLY the two fields below, clearly labelled, ready to paste. No preamble. === GENERATION PROMPT === Cover, in tight prose (hardcode the real business facts you researched):

• Who the page is for: [business name], the industry, region, "since [year]", licensed/insured. Each page targets "{{ service }} {{ city }} {{ state }}".

• Voice: match the brand voice you found. Active, scannable, ~8th-grade level. Write like a local pro who has worked in {{ city }}, not a content mill.

• LOCALIZATION MANDATE: every page must include ≥4 facts true ONLY of {{ city }} — local climate stress, neighborhoods, housing stock/age, or {{ state }} codes/permits. Never name another city. Never leave a bracket/placeholder on the page.

• SEO: exact phrase "{{ service }} {{ city }}" in the H1, first 100 words, and one H2; natural variants elsewhere; no stuffing.

• Images: "Include 3 inline images."

• Internal links: "Include 4 internal links, at least one to [parent hub URL]."

• CTAs: reference [phone] ≥3 times; [booking URL] in the closing.

• Trust: weave in [real trust signals you found] where natural.

• Banned phrases: look no further, nestled, in today's fast-paced world, when it comes to, rest assured, top-notch, we've got you covered.

• E-E-A-T: write from experience — what fails, what it costs, what to do. Goal: a page Google sees as more helpful than thin competitor pages, not a doorway page. === MARKDOWN OUTLINE === Build this structure with {# #} instructions and the three variables. Hardcode business facts as literal text. Keep it ≤4,800 characters:

{{ service }} in {{ city }}, {{ state }}

{# 45–55 word intro answering intent for {{ service }} in {{ city }}; name the city, the service, and [business name]; end with a CTA to call [phone] or book online. #}

Why {{ city }} chooses [business name] for {{ service }}

{# 2–3 sentences of credibility tied to {{ city }}: [years] serving [region], licensed & insured, [top trust signal]. #}

• {# licensing / insured #}

• {# years serving {{ city }} or response time #}

• {# guarantee or top award #}

• {# financing or 24/7 emergency #}

{{ service }} in {{ city }}, {{ state }}

{# 2–3 paragraphs on the core service, weaving in ≥3 facts true only of {{ city }} (climate, housing age, neighborhoods, {{ state }} codes). Use real knowledge of {{ city }}, {{ state }}. Close with a CTA to call [phone]. #}

Common {{ service }} problems in {{ city }} homes

{# 3–4 realistic local issues as bold mini-headers, each one sentence on cause + fix, flavored by {{ city }}'s climate and housing. #}

Our {{ service }} services in {{ city }}

{# 4–6 sub-services, each one value-packed sentence, matching what [business name] actually offers. #}

What {{ service }} costs in {{ city }}

{# Honest price ranges + factors that move them (size/age, parts, access, severity), ideally a compact table. Mention free estimates if offered. #}

What to expect when you call us

{# 4–5 step process: call → same/next-day visit → upfront quote → fix → follow-up. Mention financing if offered. #}

Areas we serve near {{ city }}

{# Name 4–6 real {{ city }} neighborhoods/zip areas + nearby towns covered. #}

{# One realistic 1–2 sentence review for {{ service }} in {{ city }}, signed with a first name + {{ city }}. #}

{{ service }} {{ city }} FAQ

{# 5 genuinely local Q&As (bold question + 1–2 sentence answer): response time in {{ city }}, permits for {{ service }} in {{ state }}, service frequency for {{ city }}'s climate, emergency availability, and one cost/warranty question. #}

Get {{ service }} in {{ city }} today

{# 2–3 sentence trust + urgency close, then CTA: call [phone] or book at [booking URL] for {{ service }} in {{ city }}. #}