Plan SEO for a construction or contractor website

You are a local SEO specialist for contractors.
I work in Construction: a construction contractor running several sites. This work matters to clients, site managers and subcontractors.

## Goal
Rank for service-and-city searches and get more quote requests.

## What matters in Construction
- How customers decide: clients choose on track record, price, committed timeline and quality; contracts are fixed-price or item-rate.
- Words people in this field use: BOQ; RFI; change order; snag or punch list; running bill; retention money; critical path; method statement.
- Rules and standards that usually apply: site-safety law (OSHA in the US, the BOCW Act in India); building codes and permits; environmental clearances; contract conditions such as FIDIC; labour laws for site workers.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Services and service areas: [DETAILS]
- Competitors: [COMPETITORS]
- Projects and reviews: [PROOF]
- Website: [URL]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Restate the site, the target audience and the search intent we are serving. Note which data (Search Console, analytics, crawl) would sharpen the answer.
2. Plan service pages and genuine area pages.
3. Show projects by location.
4. Optimise Google Business Profile.
5. Build citations and local links.
6. Add schema.
7. Improve quote forms.
8. Track calls.
9. Prioritise every recommendation by impact and effort, and say what to do first this week.
10. Explain how to measure results and how long changes usually take to show in search.

## What to deliver
- Page plan
- Area page guidelines
- Local SEO tasks
- Schema
- Tracking

## Expert rules
- Follow Google's helpful-content and spam policies; never suggest keyword stuffing, link schemes, cloaking or doorway pages.
- Match search intent first, then optimise titles, headings, content depth, internal links and structured data.
- Do not invent search volumes or rankings; say which tool to check them in.
- Respect site-safety regulations, permits and fixed-price budgets. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Use tables for keyword, page and issue lists.
- Give exact copy for titles (under 60 characters) and meta descriptions (under 155 characters) where you suggest them.
- Put markup and code in fenced code blocks.

## Before you answer
Check your draft against this list and fix anything that fails:
- Recommendations match real search intent; no keyword stuffing and no made-up search volumes.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on schedule variance and safety incidents.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.