Audit the Work, Assign the Fix, and Verify the Result

Start by creating one record for every checklist item. The record should hold the current evidence, the pass or fail decision, severity, owner, corrective action, and the validation result. That prevents a task from being marked complete merely because someone edited a page or opened a profile.

Evidence required: save the live URL, screenshot, crawl result, Search Console view, profile view, directory record, or other artifact that proves the current state. Pass or fail: define the observable condition that must be true. Severity: escalate failures that block discovery, misstate the business, or break a customer action. Owner: name the role responsible for the correction. Corrective action: specify the smallest change that resolves the documented defect. Validation: repeat the original test after the change and record the result.

Use advanced work such as schema markup, content clusters, and technical refinement only after the underlying pages and local data pass their foundational checks. If you are reviewing an existing SEO audit, require the same evidence before accepting a task as complete. The source used the first 60-90 days as an implementation reference for foundational work; treat that period as a planning window for review, not as a ranking guarantee.

Google Business Profile identity and access. Evidence required: the live profile, account access status, and current shop records. Pass or fail: pass when the correct business is claimed or otherwise properly managed, its core identity is accurate, and the listing represents the real location and services; fail for wrong ownership, material identity errors, or inaccessible management. Severity: Critical for a wrong or unmanaged profile, High for material customer-facing errors. Owner: shop manager or local marketing owner. Corrective action: resolve access and update factual profile information. Validation: reopen the live profile after processing and compare it with the shop records.

Profile field coverage and imagery. Evidence required: a field-by-field profile review and current images. The source used 10-15 photos as a working reference and 2-3 secondary categories as an example. Pass or fail: pass when hours, contact details, website, categories, services, and imagery are accurate and useful; fail when important fields are wrong, missing, or misleading. Severity: High for incorrect customer-facing information, Medium for incomplete but noncritical details. Owner: local marketing owner. Corrective action: update only information that accurately describes the shop. Validation: compare the published fields with the approved record after edits.

Business description review. Evidence required: the live description and a factual service summary from the shop. The source used 150 words as an editorial reference. Pass or fail: pass when the description accurately explains the shop, its relevant services, and service context without stuffing or unsupported claims. Severity: Medium. Owner: content owner with shop review. Corrective action: rewrite inaccurate or unclear copy. Validation: have the shop owner or manager verify every factual statement in the published version.

NAP consistency. Evidence required: side-by-side Name, Address, and Phone number records from the website, Google Business Profile, and the important directories where the shop is already listed. Pass or fail: pass when the identity data is accurate and materially consistent; fail when a listing points to an obsolete address, wrong phone number, or another conflicting business identity. Severity: High for material conflicts, Medium for harmless formatting differences. Owner: local SEO or operations owner. Corrective action: correct the inaccurate source record. Validation: revisit the edited listings and confirm the corrected data is live.

Time investment: the source estimated 2-4 hours for this pass. It also associated 20-40% with shop position improvements within 2 weeks, but no supporting source URL exists in the JSON. Preserve those values only as previously published context requiring reconciliation, not as a verified forecast.

Priority service-page coverage. Evidence required: an inventory of commercially important repair services and the live URL assigned to each one. The source suggested using the service area name 2-3 times naturally when that wording is genuinely helpful. Pass or fail: pass when each important service has a useful, indexable destination or is intentionally grouped with a closely related service; fail when a priority service exists only as a vague list item or duplicated thin page. Severity: High for a missing core service destination. Owner: SEO or content owner with technician review. Corrective action: improve, consolidate, or create the needed service page without manufacturing duplicate location or service pages. Validation: crawl the URL, confirm indexability and internal links, and review the rendered page for factual accuracy.

Structured FAQ review on service pages. Evidence required: the questions visible to users and any existing structured data attached to them. Pass or fail: pass when the FAQ content answers real customer questions and any schema matches visible content; fail when markup is inaccurate, hidden, or added solely to chase a search feature. Severity: Medium for invalid implementation. Owner: technical SEO or developer. Corrective action: repair or remove inaccurate markup while preserving useful visible answers. Validation: retest the rendered page and markup. Do not claim FAQ markup earns a Google FAQ rich result.

Citation inventory and correction. Evidence required: a list of current business listings and their NAP values. The source compared shops appearing in 10+ directories with shops appearing in 3-5, but the JSON provides no supporting source URL. Pass or fail: pass when important legitimate listings are accurate and duplicates or obsolete records are addressed; fail for material conflicts. Severity: High on prominent sources, Medium on secondary sources. Owner: local SEO owner. Corrective action: claim, correct, merge, or remove inaccurate records where the platform allows. Validation: recheck each edited listing after publication.

Review request workflow. Evidence required: the actual post-service request process, staff instructions, and sample messages. The source used 1-2 reviews per week as an operating reference. Pass or fail: pass when eligible customers are asked consistently for honest feedback without incentives, discouraging negative reviews, or selecting only satisfied customers; fail when review gating or prohibited incentives are part of the process. Severity: Critical for policy-risk practices, Medium for the absence of a repeatable process. Owner: service manager or customer-experience owner. Corrective action: standardize a neutral request that treats eligible customers consistently. Validation: inspect the live workflow and a sample of recent requests.

Time investment: the source estimated 8-12 hours over 6 weeks. It also tied this stage to top-3 Map Pack positioning within 60-90 days. Because the source provides no supporting URL for that outcome claim, use that period only as a stage for comparing post-change visibility against the pre-change baseline.

Mobile performance and usable loading. Evidence required: current PageSpeed Insights output plus a manual mobile test on the homepage and priority service pages. The source used over 3 seconds as an escalation cue. Pass or fail: pass when important content and actions remain usable and no material loading defect blocks the journey; fail when delay or rendering prevents a customer from reading, calling, or requesting service. Severity: High for broken customer actions, Medium for nonblocking performance debt. Owner: developer or site owner. Corrective action: optimize media, scripts, caching, or templates according to the documented bottleneck. Validation: rerun the same URLs and repeat the mobile journey after deployment.

Crawlability and internal-link integrity. Evidence required: Search Console findings and a crawl of status codes, internal links, directives, redirects, and canonical targets. Pass or fail: pass when priority pages are reachable and indexable as intended and internal links resolve to useful destinations. Severity: Critical for broad blocking or loss of core pages, High for broken paths to priority services. Owner: technical SEO or developer. Corrective action: repair broken links, redirects, indexability directives, or navigation. Validation: recrawl affected URLs and confirm the same defect no longer appears.

HTTPS delivery. Evidence required: browser tests and redirect checks for representative URLs. Pass or fail: pass when the secure canonical version loads without certificate warnings and alternate protocol requests resolve correctly. Severity: Critical for certificate failures, High for conflicting protocol versions. Owner: hosting or development owner. Corrective action: repair certificate or redirect configuration. Validation: retest representative URLs in a browser and crawl.

Mobile content parity. Evidence required: rendered mobile and desktop views of essential service content and actions. Pass or fail: pass when mobile users can access the same essential information and complete the same important actions; fail when responsive templates hide or break critical content. Severity: High. Owner: developer and content owner. Corrective action: repair responsive templates or conditional rendering. Validation: repeat the device test after the fix.

Time investment: the source estimated 2-4 hours for the technical audit, with repair effort varying by site. Close this stage when the documented blockers are resolved, not by claiming prevention of an unspecified algorithmic penalty.

Structured data accuracy. Evidence required: the markup emitted by relevant pages, visible page content, and validator output. The source previously associated complete schema with 10-15% click-through improvement, but no supporting source URL is present. Pass or fail: pass when markup accurately describes visible content and contains no material errors or unsupported claims; fail when it misrepresents the shop or conflicts with the page. Severity: High for misleading markup, Medium for noncritical validation errors. Owner: technical SEO or developer. Corrective action: correct the existing implementation to match the page. Validation: rerun the validator and inspect the rendered source.

Informational content selection. Evidence required: Search Console queries, customer questions, and an inventory of existing content. The source used 6-12 months as a horizon for evaluating compounding informational visibility. Pass or fail: pass when proposed topics answer real repair or maintenance questions without duplicating commercial service pages; fail when the plan is generic, repetitive, or disconnected from user demand. Severity: Low to Medium. Owner: content owner with shop subject-matter review. Corrective action: prioritize the most useful missing question and integrate it into the site's internal linking. Validation: confirm indexability, factual accuracy, and that the page serves a distinct intent.

Review response quality. Evidence required: recent review history and the shop's response policy. The source used 48 hours as an operating reference. Pass or fail: pass when responses are professional, privacy-conscious, factual, and used where useful; fail for abusive, misleading, or privacy-invasive replies. Severity: High for harmful public responses, Medium for an unmanaged process. Owner: customer-experience lead. Corrective action: establish response guidance and route disputes to an appropriate private channel. Validation: inspect a sample of recent replies after the policy is in use.

Video usefulness and production. Evidence required: an inventory of current video assets and where they appear. The source contained an unsupported 15-20% local visibility statement and suggested beginning with 3-5 videos of 60-90 seconds each. Pass or fail: pass when any produced video helps users understand the actual shop, team, or service and is factually accurate; fail when it exists only to manufacture a claimed search signal. Severity: Low because video is optional. Owner: marketing owner. Corrective action: produce or revise only material tied to a clear customer-information need. Validation: verify playback, captions where applicable, factual accuracy, and placement.

Time investment: the source estimated 4-6 hours per month for this stage and used 6+ months as a longer review horizon. Evaluate advanced work with the shop's own search and conversion data rather than assuming the preserved historical percentages are causal.

If you have 4 weeks: resolve failed profile and NAP checks first, then validate the commercial page assigned to each of your top 3 services. The stage is complete only when the evidence changes from fail to pass.

If you have 12 weeks: complete all foundational local and service-page checks, assign unresolved technical defects, and establish a repeatable review-request process that follows policy.

If you have 6+ months: maintain the technical and local checks while adding advanced work only where evidence shows a genuine content, structured-data, or customer-information gap.

Agency evaluation warning: a promise of ranking gains in 2-3 weeks is not proof of competent work. Require a provider to show the original defect, the change made, the responsible owner, and the validation evidence. The source used 30-60 days as a minimum review window for ranking movement from solid work; treat that as a reassessment period, not a guaranteed outcome.

Common sequencing failure: publishing more content while business data, crawlability, key service pages, or customer actions still fail the checklist wastes effort. Resolve verifiable foundational defects first, retest them, and only then expand.