A verification-first SEO checklist for real estate agents

This checklist is for independent Realtors, small teams, and agents who can edit or influence their own web presence. If a brokerage controls the site centrally, use the linked audit guide to document gaps and route them to the person who owns the platform.

Use one evidence record per check. The quick-pass items may take 1-5 minutes each, while broader structural work can continue over 3-6 months. For every item, capture the evidence required, mark pass or fail against the stated condition, assign a severity and owner, record the corrective action, and repeat the validation step after the change.

• Quick checks (12 items): Evidence should be available from the page, Google Business Profile, or Google Search Console. The first review can fit within 2 hours when access is already available.
• On-page optimization (14 items): Verify titles, descriptions, headings, copy, internal links, media text, and local usefulness on the pages that matter to buyers and sellers.
• Technical SEO (10 items): Verify crawl access, indexability, mobile behavior, speed evidence, canonical handling, broken-page behavior, and structured data accuracy.
• Authority and citations (7 items): Verify business information, legitimate local mentions, useful neighborhood content, and internal link paths without using reciprocal-link schemes as a shortcut.
• Compliance and trust (4 items): Verify advertising language, IDX or MLS display requirements, review practices, and geographic claims with the appropriate broker, MLS, or legal reviewer when needed.

A pass means the required evidence exists and the validation step reproduces the expected state. A fail is actionable only after an owner and corrective action are named.

Use these as verification tasks, not ranking promises. A typical first pass may take 5-20 minutes per check when accounts and editing access are ready. Record screenshots, exported reports, or page URLs as evidence so another person can reproduce the finding.

1. Claim and verify the Google Business Profile. Evidence: the profile manager shows your authorized access and the live profile reflects the real business. Pass: ownership and core identity fields are verified. Fail: the profile is unclaimed, inaccessible, or materially inaccurate. Severity: high for ownership or identity errors. Owner: profile administrator. Corrective action: complete the supported verification or access-recovery process and correct factual fields. Validation: reopen the live profile and compare it with the business's website and records. Reserve about 10 minutes for the initial evidence capture when access is already available.
2. Review the GBP business description. Evidence: copy the current description into the audit record. Pass: it accurately describes services and genuine service areas without unverifiable superlatives or keyword stuffing. Fail: it is missing, outdated, misleading, or written mainly for keywords. Severity: medium. Owner: profile editor. Corrective action: rewrite within the platform limit and remove claims you cannot substantiate. Validation: compare the published description with current offerings and location facts. The source draft referenced 750 characters and a 15 minute editing window; use those only as operating constraints where they still apply, not as ranking factors.
3. Check profile media for accuracy and usefulness. Evidence: review the visible photos and any video. Pass: media is current, relevant, correctly associated with the business, and free of misleading representations. Fail: important media is obsolete, incorrect, or absent where you have useful media to publish. Severity: low to medium. Owner: profile editor. Corrective action: add or replace accurate media through the profile interface. Validation: confirm the intended media appears on the live profile. The source draft allocated 10 minutes for this review; that is an operating estimate only.
4. Inspect the homepage title tag. Evidence: capture the rendered title from the page source or an SEO inspection tool. Pass: the title is unique, accurate, concise enough to be useful, and naturally reflects the agent or brokerage and the primary market actually served. Fail: it is missing, duplicated, misleading, or generic. Severity: high on a primary landing page. Owner: site editor. Corrective action: rewrite the tag around the page's real purpose. Validation: recrawl the page and confirm the intended title is present. The source draft assigned about 5 minutes for the edit.
5. Inspect the homepage meta description. Evidence: capture the current meta description and the page's main value proposition. Pass: the description accurately summarizes the page, includes useful location context where relevant, and avoids claims the business cannot support. Fail: it is absent, duplicated, stuffed, or misleading. Severity: medium. Owner: site editor. Corrective action: write a concise description for searchers rather than a guarantee of how Google will display it. Validation: recrawl the page and confirm the tag. The prior draft used 155 characters as an editorial target and included 2010 in an example business-history statement; retain those as historical drafting examples only, not as requirements. Allow about 5 minutes for the field update.
6. Review the NAR directory profile if one exists for the agent. Evidence: save the profile URL and compare business name, contact information, and brokerage details with current records. Pass: the listing is accurate and consistent. Fail: stale or contradictory business data is visible. Severity: medium. Owner: directory profile owner. Corrective action: request or make factual corrections through the directory's supported process. Validation: revisit the live profile after the change. The source draft used a 10 minute review estimate.
7. Inspect recent listing-page metadata. Evidence: capture the current title tag and meta description for 3 representative listings. Pass: each page has accurate, page-specific metadata the platform allows you to control. Fail: multiple pages reuse generic text or expose incorrect property details. Severity: medium to high depending on page importance. Owner: site or IDX editor. Corrective action: replace editable generic metadata with accurate page-specific text. Validation: recrawl each sampled page after publishing. The source draft allowed about 15 minutes per sampled listing.
8. Find and repair a broken internal link. Evidence: export the broken-link result from a crawler or inspection tool. Pass: the sampled link resolves to the intended live destination without an unnecessary redirect chain. Fail: it points to a missing, incorrect, or irrelevant page. Severity: medium for navigation paths and low for isolated minor references. Owner: site editor. Corrective action: update or remove the broken reference. Validation: recrawl the source page and open the destination. The source draft budgeted 10 minutes for a simple repair.
9. Review existing Google Business Profile posts as content records, not ranking levers. Evidence: capture the live post history and current messaging. Pass: any published posts are accurate, current, and useful to prospective clients. Fail: posts contain expired, misleading, or unsupported claims. Severity: low unless the content is materially misleading. Owner: profile editor. Corrective action: revise or remove outdated posts and publish only when there is a real update worth communicating. Validation: confirm the live profile shows the intended content. The source draft referred to 3 posts, a 7 day period, and a 10 minute task window; treat those as historical operating examples rather than documented ranking guidance.
10. Identify legitimate local relationship opportunities. Evidence: list 5 relevant organizations or businesses with a real connection to the markets you serve and note why a mention or link would help readers. Pass: outreach is editorially justified and does not require a reciprocal link. Fail: the plan depends on exchanging links solely to manipulate ranking signals. Severity: high for manipulative link schemes, otherwise low. Owner: marketing lead. Corrective action: replace quid-pro-quo outreach with genuine partnerships, citations, sponsorship documentation, or useful local resources where appropriate. Validation: review any resulting mention for accuracy and editorial relevance. The source draft allocated 15 minutes for initial outreach preparation.
11. Test the site on a phone. Evidence: record screenshots and the affected page URLs for navigation, forms, images, maps, and listing interfaces. Pass: core tasks can be completed without clipped content, unreadable text, blocked controls, or unusable forms. Fail: a core interaction breaks on the tested device. Severity: high for contact or listing-search failures. Owner: web developer or platform vendor. Corrective action: repair the responsive layout or component. Validation: retest the same task on the same device and one additional common viewport. The source draft used 10 minutes for the first manual pass and another 10 minutes for documentation.
12. Set up or confirm Google Search Console access. Evidence: verified property access, current indexing reports, and a saved baseline export. Pass: the correct property is verified and the team can review index and performance data. Fail: the property is missing, inaccessible, or represents the wrong site variant. Severity: high because later checks depend on reliable evidence. Owner: site administrator. Corrective action: verify the correct property and grant appropriate access. Validation: confirm the property receives current data and that key pages can be inspected. The source draft estimated 20 minutes for setup plus the first review.

Listing copy should help a searcher understand the property and its location without overstating facts. A phrase such as "3-bed colonial in Riverside" can be useful only when those details are accurate and the page is genuinely about that property.

For each sampled listing or neighborhood page, keep a page-level evidence record and use these checks:

1. Local context in the opening copy. Evidence: capture the first paragraph and property facts. Pass: the neighborhood or locality is named naturally when it is accurate and useful. Fail: the page omits material local context or inserts place names that do not fit the property. Severity: medium. Owner: listing editor. Corrective action: revise the opening for factual local relevance. Validation: compare the published copy with the listing record.
2. Specific query coverage. Evidence: note the search intent the page is meant to satisfy and the phrases already present. Pass: copy answers that intent naturally. Fail: the page is written around forced keyword variants rather than useful property facts. Severity: medium. Owner: content editor. Corrective action: replace stuffing with accurate language and, where genuinely relevant, a small set of 2-3 descriptive long-tail phrases. Validation: reread the page as a buyer or seller and confirm every phrase is supported by the property or location.
3. Description depth. Evidence: save the current copy and note whether it answers practical questions about the property. Pass: the description is as detailed as needed to be useful and unique. Fail: it is thin boilerplate or padded repetition. Severity: medium. Owner: listing editor. Corrective action: add verified details, context, and distinctions rather than filler. Validation: compare the revised version with source facts. The source draft used a 250-400 word range as an editorial example; treat it as a drafting reference, not a ranking threshold.
4. Heading hierarchy. Evidence: capture the rendered headings and document outline. Pass: the H1 states the page topic, H2 headings organize major sections, and H3 headings are used only where subordinate structure is useful. Fail: headings are missing, misleading, or used only for visual styling. Severity: medium. Owner: site editor. Corrective action: repair the semantic hierarchy. Validation: re-inspect the rendered heading outline.
5. Internal link to useful location context. Evidence: identify any link from a listing to a genuine neighborhood or community page. Pass: the destination adds useful location-specific information and is relevant to the property. Fail: the link is absent where context would help, or points to thin or unrelated content. Severity: low to medium. Owner: content editor. Corrective action: add a relevant internal link only when a substantive destination exists. Validation: open the link and confirm the destination is live and useful.
6. MLS identifier accuracy. Evidence: compare the page with the authoritative listing feed or record. Pass: any displayed identifier is correct and allowed by the applicable MLS rules. Fail: the identifier is wrong, stale, or displayed contrary to applicable rules. Severity: high for factual or compliance errors. Owner: IDX or listing administrator. Corrective action: correct the source data or template. Validation: refresh the page and compare again with the authoritative record.
7. Image alternative text. Evidence: inspect meaningful listing images and their alt attributes. Pass: alt text describes the image accurately where text alternatives are needed and does not repeat keywords mechanically. Fail: important images have misleading, irrelevant, or empty alternatives without a valid reason. Severity: medium for accessibility-relevant images. Owner: content editor or platform vendor. Corrective action: add concise factual alternatives supported by the image. Validation: re-inspect the rendered HTML and test representative images with assistive-technology expectations in mind.
8. Title-tag uniqueness and accuracy. Evidence: export titles for the sampled template and compare them with visible page topics. Pass: important pages have titles that accurately distinguish their purpose without repetitive boilerplate overwhelming the useful text. Fail: titles are missing, materially duplicated, or describe a different property or market. Severity: medium to high by page importance. Owner: site editor or platform vendor. Corrective action: revise the editable template or page title using supported facts. Validation: recrawl the affected pages and compare the rendered titles.
9. Meta-description quality. Evidence: export the current descriptions for representative pages. Pass: each description, where used, is accurate, page-specific, and written for a prospective client rather than as a ranking promise. Fail: descriptions are empty, misleading, or repeated across materially different pages. Severity: medium. Owner: content editor. Corrective action: rewrite editable descriptions around the page's actual information and intent. Validation: recrawl the pages and confirm the intended metadata is present.
10. Canonical and indexability alignment. Evidence: capture the canonical element, robots directives, HTTP response, and Search Console status for sampled pages. Pass: these signals agree with the deliberate indexing decision for the page. Fail: a page intended for search is blocked or canonicalized elsewhere without reason, or a duplicate variant is indexable contrary to the site's plan. Severity: high for template-wide conflicts. Owner: developer or IDX vendor. Corrective action: align canonical, robots, and platform settings with the chosen indexability policy. Validation: recrawl the page and inspect it again in Search Console.
11. Neighborhood-page usefulness. Evidence: compare the page with other location pages and list the information unique to that genuine place. Pass: the page contains useful, accurate location-specific material for an area the agent actually serves. Fail: the page is interchangeable boilerplate or targets a nominal market without meaningful local information. Severity: medium. Owner: content lead. Corrective action: improve the page with substantiated local information or consolidate it when distinct value cannot be supported. Validation: compare the revised page side by side with neighboring location pages.
12. Listing-status and stale-page handling. Evidence: sample active, pending, sold, expired, or otherwise changed listings and compare website status with the authoritative feed or record. Pass: the displayed status is accurate and the page behavior follows the site's deliberate retention and indexing policy. Fail: stale status, misleading availability, or broken redirects create a factual or navigation error. Severity: high for misleading availability. Owner: IDX administrator or platform vendor. Corrective action: repair feed mapping, page state, or destination logic. Validation: refresh and recrawl the sampled listing states.
13. Contact-path integrity. Evidence: submit or test representative contact actions using an approved test process and record the destination owner. Pass: the call, form, email, or scheduling action reaches the intended business workflow without exposing incorrect contact details. Fail: a primary conversion path is broken, routes to the wrong recipient, or asks for information the business does not need. Severity: high. Owner: site administrator or CRM owner. Corrective action: repair the form, routing, contact field, or integration. Validation: repeat the same approved test and confirm receipt.
14. Agent and brokerage identity consistency. Evidence: compare visible names, brokerage affiliation, contact information, and required disclosures across the page templates that present the agent. Pass: identity details are current, internally consistent, and compliant with applicable display requirements. Fail: templates show stale affiliation, contradictory names, or missing required information. Severity: high when the discrepancy could mislead a client or violate a rule. Owner: site editor with broker review as appropriate. Corrective action: update the source-of-truth fields or affected templates. Validation: recrawl representative pages and compare them with current business records.

Platform limits are themselves an audit finding. If the real estate CMS or IDX does not expose editable titles, descriptions, headings, canonicals, or image text, record that limitation, its affected templates, the owner responsible for vendor escalation, and the validation method you will use after any platform change.

Technical checks should produce reproducible evidence. Work through these 10 items with Search Console, browser inspection, a crawler, and the platform's own settings where available.

• Mobile rendering and interaction. Evidence: screenshots and task notes from representative mobile pages. Pass: core navigation, search, listing details, and contact actions work on the tested device. Fail: content or controls are inaccessible or unusable. Severity: high for blocked core tasks. Owner: developer or vendor. Corrective action: repair the responsive component. Validation: rerun the same tasks after release. The prior draft's 60% figure lacked a supporting source URL in the source JSON, so treat it as a historical claim requiring source reconciliation rather than a verified benchmark.
• Page performance. Evidence: save PageSpeed Insights output and note whether the data is lab or field data. Pass: there is no material performance defect blocking the intended user experience, and any Core Web Vitals assessment is interpreted according to current Google documentation. Fail: large images, scripts, or rendering work cause a reproducible problem that should be fixed. Severity: medium to high by affected template. Owner: developer or vendor. Corrective action: optimize the measured bottleneck. Validation: rerun the same test after deployment. The earlier draft used 2.5 seconds as a target; preserve it as a historical triage reference, not a guaranteed ranking cutoff.
• Structured data accuracy. Evidence: capture the structured data emitted on representative templates and test it with an appropriate validator. Pass: markup describes visible page content accurately, uses supported properties, and does not invent business, person, offer, or listing facts. Fail: markup is invalid, misleading, duplicated in conflict, or unrelated to the page. Severity: medium to high depending on error scope. Owner: developer or CMS vendor. Corrective action: correct or remove inaccurate markup. Validation: retest the published page. Do not treat schema as a special requirement for Google AI Overviews or as a guaranteed ranking factor.
• XML sitemap coverage. Evidence: save the submitted sitemap locations and compare representative URLs with the pages intended for indexing. Pass: canonical indexable pages are discoverable and obsolete or noncanonical variants are not unnecessarily promoted. Fail: important pages are missing or unwanted URLs dominate the sitemap. Severity: medium. Owner: developer or platform vendor. Corrective action: update sitemap generation or submission. Validation: fetch the refreshed sitemap and compare the sampled URLs again.
• Robots rules. Evidence: archive the current robots file and test affected URLs. Pass: crawling rules match the intended access policy. Fail: important pages are accidentally blocked or unwanted crawl paths are unintentionally exposed. Severity: high for sitewide blocking. Owner: developer. Corrective action: repair the rule and coordinate with indexability settings. Validation: retest the affected URLs after deployment.
• HTTPS and mixed-content behavior. Evidence: capture the browser security state and redirect behavior. Pass: the intended secure URL loads consistently and embedded assets do not produce material mixed-content errors. Fail: insecure assets, certificate problems, or inconsistent redirects remain. Severity: high for trust or access failures. Owner: hosting or development owner. Corrective action: repair certificates, asset references, and redirects. Validation: reload the canonical URL and confirm the https:// version is the intended destination.
• Duplicate and canonical handling. Evidence: compare canonical tags, indexability, and content across listing and filter variants. Pass: canonical signals match the site's deliberate indexing strategy and do not misidentify another party's page as the preferred version without a sound reason. Fail: canonicals conflict, point to irrelevant URLs, or are absent where duplicate variants create ambiguity. Severity: high for widespread template errors. Owner: IDX or development owner. Corrective action: define and implement the preferred-URL policy. Validation: recrawl affected variants and inspect Search Console.
• Internal link architecture. Evidence: export crawl depth and inlink data for home, neighborhood, service, and listing pages. Pass: important pages are reachable through useful contextual links. Fail: key pages are orphaned, buried without reason, or linked through misleading anchor text. Severity: medium. Owner: site editor. Corrective action: add or repair logical internal paths. Validation: recrawl and confirm the intended pages are reachable.
• 404 behavior. Evidence: open a known 404 URL and sample expired listing destinations. Pass: missing resources return a real 404 status while the error page offers useful navigation without pretending the URL exists. Fail: missing pages return a success response, redirect irrelevantly, or strand users. Severity: medium. Owner: developer or IDX vendor. Corrective action: correct status handling and provide appropriate navigation. Validation: retest the same missing-page case after the change.
• Core Web Vitals triage. Evidence: save current field and lab reports for representative templates and note the metric names shown by the tool. Pass: the team understands which current Core Web Vitals metrics are passing or failing and has evidence for any remediation priority. Fail: decisions are based on stale metric names, a single synthetic run, or unsupported ranking claims. Severity: medium. Owner: developer or performance owner. Corrective action: diagnose the current metric failure and test the fix. Validation: rerun lab tests and monitor field data when available. The prior draft used scores above 90 and below 50 as competitive cutoffs; preserve them only as historical internal triage labels, not documented ranking thresholds.

Citations are public mentions of business identity details such as name, address, and phone number. Treat consistency as a data-quality task and avoid presenting any directory, posting pattern, or link tactic as a guaranteed ranking factor.

1. Audit existing citations. Evidence: collect the current business details shown on the most relevant directories and local profiles. Pass: name, contact details, and brokerage information are materially accurate and consistent with the business's records. Fail: stale or contradictory details could confuse a prospective client. Severity: medium, or high for wrong contact data. Owner: local presence manager. Corrective action: request factual corrections through each platform's supported process. Validation: revisit the public records after updates.
2. Review claimed directory profiles. Evidence: save profile URLs and ownership status for relevant real estate and local directories. Pass: profiles the business actually uses are accurate, properly claimed where supported, and not padded with unverifiable claims. Fail: a material profile is inaccessible, inaccurate, or misleading. Severity: medium. Owner: directory profile owner. Corrective action: correct or reclaim the profile using the platform's process. Validation: compare the live profile with current business records.
3. Create useful neighborhood content only where justified. Evidence: inventory existing location pages and the unique facts each provides. Pass: each page represents a genuine place the agent serves and contains useful location-specific information. Fail: pages differ mainly by swapped place names or exist only to target a nominal service area. Severity: medium. Owner: content lead. Corrective action: consolidate thin pages or improve only those that can support distinct local value. Validation: compare pages side by side for real informational differences. The prior draft suggested 3-5 pages as a planning example, not a rule that every market needs its own page.
4. Evaluate local backlink opportunities. Evidence: document the relationship, editorial reason for a mention, and destination page. Pass: any link can stand on its own as useful attribution, sponsorship, membership, citation, or editorial reference. Fail: the arrangement requires trading links solely to influence rankings. Severity: high for manipulative schemes. Owner: marketing lead. Corrective action: replace exchange-based outreach with legitimate relationship or content activity. Validation: review the published mention and confirm it is accurate and contextually useful.
5. Review market-report content. Evidence: retain the underlying data source, publication date, geographic scope, and methodology used for any market commentary. Pass: the report is current for its stated period, the source is identifiable, and the analysis does not overclaim causation. Fail: the report uses stale numbers, unsupported conclusions, or unclear provenance. Severity: high for misleading market claims. Owner: content owner with broker review as required. Corrective action: update or qualify the analysis. Validation: reconcile each material statement with the source data. The source draft included January 2024 as an example report period; treat it as a historical example, not a current-data claim.
6. Assess local editorial contributions. Evidence: save the publication brief, authorship terms, and destination link if any. Pass: the contribution offers useful local expertise and the publication relationship is legitimate. Fail: the sole purpose is an artificial backlink or the article contains unsupported claims. Severity: medium to high. Owner: content or PR lead. Corrective action: revise the contribution around factual reader value or decline the placement. Validation: review the published article for accuracy and link context. The prior draft mentioned a 500-word contribution as an example format, not a performance threshold.
7. Review internal link equity paths. Evidence: export inlinks to important neighborhood, service, and listing pages. Pass: internal links reflect user journeys and page relationships. Fail: important pages are isolated or linked with manipulative, repetitive anchors. Severity: medium. Owner: site editor. Corrective action: add relevant contextual links from appropriate pages. Validation: recrawl and confirm the updated paths.

Compliance checkpoint: Third-party profiles, neighborhood copy, and testimonials should use factual, non-discriminatory language. Review the linked common SEO mistakes guide for related implementation risks, and route legal or licensing questions to the appropriate professional rather than inferring compliance from SEO tools.

This is educational content, not legal or real estate licensing advice. Verify advertising, licensing, and MLS obligations with the professionals and organizations that govern your practice.

The source draft references the Fair Housing Act at 42 USC 3601-3619 and the NAR Code of Ethics Article 12. Treat those references as prompts for compliance review, not as a complete statement of every applicable federal, state, local, brokerage, or MLS requirement.

1. Fair Housing advertising review. Evidence: retain the page copy, listing facts, and source for any demographic, safety, school, commute, or neighborhood statement. Pass: descriptions focus on verifiable property and location facts and do not express preferences or limitations tied to protected characteristics. Fail: copy contains discriminatory language, steering implications, or factual claims that cannot be supported. Severity: critical. Owner: agent and broker or compliance reviewer. Corrective action: remove or rewrite problematic language and obtain appropriate review when needed. Validation: compare the revised copy with authoritative source facts and applicable policy. A phrase such as "2 blocks from Jefferson Elementary" is only appropriate if accurate and if its use complies with applicable guidance.
2. IDX and MLS display review. Evidence: save the current MLS or IDX rules that apply to the site and capture representative listing pages. Pass: required attribution, disclaimers, data handling, refresh behavior, and display restrictions are implemented as the governing rules require. Fail: the site omits required disclosures or shows data in a prohibited way. Severity: critical. Owner: broker, IDX administrator, and vendor as appropriate. Corrective action: correct the template or feed configuration against the actual rule text. Validation: recheck representative listings against the current governing documentation.
3. Testimonial and review practice review. Evidence: document the request process, any templates, incentives, moderation rules, and published testimonials. Pass: eligible customers are asked consistently for honest feedback without incentives, discouraging negative feedback, or selecting only satisfied customers, and published testimonials are authentic and accurately represented. Fail: the process gates reviewers, offers rewards tied to sentiment, fabricates identity, or edits meaning. Severity: critical. Owner: marketing lead with broker or legal review as needed. Corrective action: stop the problematic practice, revise request language, and correct misleading testimonials. Validation: inspect the live request flow and a sample of published reviews after remediation.
4. Service-area transparency review. Evidence: compare website claims, Google Business Profile service areas, brokerage records, and actual markets served. Pass: geographic claims are accurate and do not imply a physical office or service capability that does not exist. Fail: the site or profile overstates territory or creates nominal location pages without useful location-specific content. Severity: high. Owner: agent or profile manager with broker review as needed. Corrective action: correct the public claims and remove unsupported location targeting. Validation: compare the live website and profile with current business records.

Compliance findings override ordinary SEO priorities. A search tactic should not be kept merely because it appears to attract traffic when the underlying advertising, review, listing, or location claim is inaccurate or noncompliant.

If you have 2 hours this week: Complete the 12 quick checks, save the evidence for each, and fix only defects you can validate safely. Do not treat a completed task as proof that rankings will move.

If you have 4-6 hours over the next review stage: finish unresolved quick checks and sample on-page work. Rewrite 5-10 important listing or service pages only where the evidence shows inaccurate, duplicated, thin, or poorly structured content. Recheck the published version after every edit.

If you have 10-15 hours for the technical stage: add crawl, indexability, mobile, performance, canonical, structured-data, sitemap, robots, and broken-page checks. Prioritize sitewide defects before cosmetic edits because a template problem can affect many URLs at once.

If you are planning for 6+ months: build repeatable maintenance around genuine local content, citation accuracy, and legitimate authority development. A planning batch of 3-5 neighborhood guides is useful only when each page represents a real place you serve and can contain distinct, useful information.

What not to do: do not chase broad keywords without a real audience need, do not create a 5,000-word article merely to hit a length target while 20 important pages still have known defects, do not buy or trade links for ranking manipulation, and do not stuff property copy with repeated phrases. The checklist is complete only when the evidence, owner, corrective action, and validation state are recorded for each finding.