Decide What to Fix on an Optometry Website Before Spending on More SEO

This audit is for an optometry owner, administrator, marketing lead, or technical partner who needs to decide which search problems are real, which are merely observations, and which require specialist review before action. The deliverable is a traceable issue log: each entry should show what was observed, why it matters to the practice, who owns the next step, and how the team will know the condition changed.

Move through the work in sequence. Establish technical accessibility before interpreting content performance. Reconcile local practice data before attributing visibility changes to content. Review patient-facing service information before adding new topics. Handle privacy, advertising, and clinical-claim questions as a separate risk stream rather than treating them as ordinary on-page optimization.

Evidence required: For every finding, capture the affected page, profile, template, or workflow; the dashboard, browser check, crawl export, or practice record that exposed it; and a dated screenshot or export when practical. Use the optometry SEO timeline guidance to distinguish discovery, early coverage, meaningful visibility, and sustained contribution, not as a promise that a change must occur by a particular date.

Severity: Use critical for conditions that can block access, publish materially inaccurate practice information, expose sensitive information, or create a serious review concern. Use high for defects that impair an important service or location path. Use medium or low for quality improvements whose impact is narrower or uncertain.

Owner: Assign the person who can actually change the affected system: developer for templates and crawl controls, practice operations for office data, editorial or clinical staff for patient information, and the responsible legal, medical, or regulatory reviewer for questions outside the SEO team's authority.

Corrective action: Write the smallest change that addresses the documented defect. Avoid broad instructions such as 'improve SEO' or 'add more content.' A correction should name the page, record, field, template, or workflow that will change and the acceptance condition.

Validation step: Re-run the same check that found the problem. A deployed edit is not automatically a resolved finding. Close the item only when the original evidence source shows the intended state, or document why the result remains uncertain and needs escalation.

This stage tests whether search systems and prospective patients can reach the pages that matter and receive a usable version of them. Do not interpret a technical metric as proof of a ranking cause. The audit task is to document reproducible failures, identify affected templates, and separate site-wide defects from isolated page issues.

Evidence to capture before assigning a technical fix

• Mobile interaction: Open representative service, location, provider, and contact pages on a phone. Record blocked navigation, unreadable text, controls that overlap, tap targets that fail, and booking or contact flows that cannot be completed.
• Performance screening: Save PageSpeed Insights output for representative templates. The source audit uses 60 for mobile and 80 for desktop as internal triage references. Treat them as screening values to investigate, not as Google ranking guarantees or universal pass thresholds.
• Crawl sample: If you use Screaming Frog, the source notes a free crawl allowance of 500 URLs. Confirm current product limits before relying on that allowance, and use the crawl to find redirect chains, duplicate destinations, canonical conflicts, and inaccessible internal links.
• Broken responses: Export important internal links that return 404 responses, especially links from navigation, service pages, provider pages, location pages, and conversion paths. Record both the source page and the intended destination before changing anything.
• Core Web Vitals screening: The source flags LCP above 4 seconds and CLS above 0.25 for investigation. Preserve those values as audit triggers while checking current official documentation before treating them as standards.
• Indexing evidence: In Google Search Console, compare important URLs with their indexing state and reported reason. A page that is not indexed can be an intentional exclusion, a duplication outcome, a crawl issue, or another condition; record the stated evidence instead of assuming the cause.
• Secure and consistent delivery: Check that key pages resolve to the intended secure version, that canonical signals agree with the preferred page, and that forms and scripts do not visibly fail during normal patient use.

Evidence required: Keep URL-level screenshots or exports, the affected template type, the observed browser or crawl behavior, and the Search Console state where relevant. A score without the affected page is weak evidence because it does not tell the owner what to repair.

Severity: Critical when an important page or patient-contact path is unavailable, insecure, or unintentionally excluded. High when a recurring template defect affects major service or location pages. Lower severity is appropriate for isolated defects with no clear access or usability consequence.

Owner: Assign crawl controls, redirects, templates, performance, and rendering defects to the developer or technical SEO owner. Assign broken destination decisions to the content or site owner who knows what the page should resolve to. Use the optometry SEO checklist only to organize follow-up tasks, not to replace the evidence captured here.

Corrective action: Fix the specific technical condition: restore or redirect a broken destination, remove an unintended block, reduce the offending template payload, correct a canonical conflict, or repair the mobile interaction. Do not bundle unrelated changes into the same ticket if they cannot be validated together.

Validation step: Repeat the browser test, crawl, and Search Console inspection on the same affected pages after deployment. Keep the finding open if the source still reports the problem, if the page resolves differently than intended, or if the evidence is too ambiguous to support closure.

This stage asks whether each real optometry office is represented accurately enough for patients and local search systems to identify the practice, its hours, services, and contact options. Keep website evidence and profile evidence separate, then compare them. The related optometry statistics page can provide context only where its source and limitations are documented.

Google Business Profile and review evidence

Compare the profile name, address, phone, regular and special hours, primary and secondary categories, appointment destination, service list, and practice-owned imagery against current internal records. Record discrepancies rather than treating profile completeness as evidence of a ranking outcome. Category selection should describe the services actually provided at that office, and edits should follow current platform rules.

For reviews, capture total count, visible recency, rating distribution, and the practice's solicitation process without treating any of those observations as a guaranteed ranking lever. If one internal comparison shows 80 reviews with no new feedback in 6 months while another practice shows 40 with more recent activity, record only the observed difference. That comparison does not establish why either listing ranks where it does.

Review requests should go to eligible patients consistently and ask for honest feedback without incentives, suppression of negative feedback, or selective routing of only satisfied patients. Public responses should avoid patient-specific clinical details and follow the practice's approved privacy and communications process.

Citation and identity evidence

Search important healthcare, mapping, insurer, and local directories for the practice's current name, address, phone, and website destination. Record duplicates, former addresses, disconnected numbers, alternate business names, and listings that point to the wrong office. Use the practice's authoritative records as the comparison source instead of normalizing every directory to whichever version appears most often.

Location-page evidence

For a genuine physical office, verify that the corresponding website page contains useful location-specific information such as the correct contact details, clinicians who practice there, access or parking information where relevant, and services actually available at that office. Do not create a dedicated page merely because a city is a nominal service area; the page should represent a real location and provide information a patient can use.

Evidence required: Save profile screenshots, practice records, directory URLs in the audit working file, duplicate-listing evidence, and the specific location page being assessed. Note the date because local data and profile features can change.

Severity: Critical for materially wrong contact or access information on an active office. High for duplicate profiles, conflicting identity data, or a location page that misrepresents where care is available. Medium for incomplete but accurate supporting details.

Owner: Practice operations should approve authoritative office data. The local SEO owner can submit profile and citation corrections. Website changes belong to the site or content owner. Review-response policy and privacy-sensitive wording should follow the practice's approved reviewer and communications process.

Corrective action: Correct the authoritative record first, then update each affected profile, directory, and genuine location page to match it. Merge or remove duplicates through the platform's supported process rather than creating additional listings to work around a conflict.

Validation step: Recheck the live profile, directory records, and location page after changes propagate. Mark the issue resolved only when the patient-facing information is accurate and the duplicate or conflicting record is no longer creating ambiguity.

This stage evaluates whether the website accurately explains the eye care the practice actually provides and whether those pages answer the questions a prospective patient needs before contacting the office. The audit should distinguish a missing information need from a desire to publish more pages. It should also separate clinical accuracy from search performance so editorial decisions can be reviewed by the right people.

Service coverage and page-purpose evidence

Create an inventory from the practice's current service records, then map each real service to the page intended to explain it. Review comprehensive eye exams, contact lens fitting, specialty lenses, dry eye care, myopia management, pediatric eye care, glaucoma monitoring, diabetic eye exams, low vision care, urgent eye concerns, and optical services where they are genuinely offered. For each mapped page, record the page purpose, intended audience, primary conversion path, and whether its H1 accurately names the subject without overstating credentials or outcomes.

Evidence required: Service inventory approved by the practice, page URL, page purpose, clinician or reviewer responsible for factual accuracy, and notes showing whether the information is complete enough for a patient to understand the service and next step.

Severity: High when a major offered service has no accurate page or when a page materially misstates availability, provider qualifications, or what the patient should expect. Medium when information exists but is fragmented or unclear.

Owner: Editorial or marketing owns page structure, but clinical statements should be owned or reviewed by the qualified practice reviewer. Developers own template defects that prevent the intended page from rendering or being indexed.

Corrective action: Consolidate duplicate page purposes, create or revise a page only for a real service or patient information need, and make the next action clear without implying a treatment outcome or guaranteed appointment result.

Validation step: Re-read the published page against the approved service inventory and confirm that the intended topic, provider context, office availability, and patient next step are all accurate.

Search-query and intent evidence

Use Google Search Console to compare each important page with the queries already producing impressions. Look for mismatches such as a dry eye page appearing only for branded searches, an overview page receiving unrelated service queries, or several pages competing for the same patient question. Treat this as observed search coverage, not as proof that a particular wording change will improve rankings.

Evidence required: Query export, associated landing page, date range used for comparison, and notes on whether the query represents the service and decision stage the page is meant to support.

Severity: High when an important service page is absent from relevant search coverage because of an obvious index or page-purpose defect. Medium when the evidence suggests ambiguous targeting but not a blocking condition.

Owner: SEO or editorial owns query analysis; clinicians or practice leaders confirm which services and descriptions are accurate.

Corrective action: Clarify page purpose, headings, internal links, and patient-facing explanations where the evidence supports a mismatch. Avoid manufacturing pages for every query variant or duplicating city and service combinations without distinct value.

Validation step: Recheck indexing and query-to-page alignment after the revised page has been crawled and has enough observation time to evaluate, noting uncertainty where the evidence remains sparse.

Authorship, sourcing, and review evidence

For health-related pages, confirm that users can identify who wrote or reviewed the material, what relevant qualifications support the content, when the page was reviewed, and whether claims that need support are tied to appropriate sources. Do not treat E-E-A-T as a score or a markup field. Use attribution because patients and reviewers need to understand who stands behind the information.

Evidence required: Visible author or reviewer information, credentials where relevant and accurate, review date, cited support for material health claims, and internal approval notes when the practice uses a formal review workflow.

Severity: High for unsupported or misleading health claims. Medium for missing attribution or stale review information on important patient education pages. Lower severity may apply to minor editorial gaps that do not affect factual interpretation.

Owner: Editorial staff own presentation and citations; qualified clinical reviewers own medical accuracy; practice leadership owns credential verification.

Corrective action: Attribute content accurately, remove or qualify unsupported claims, update obsolete information, and document reviewer approval where the practice requires it.

Validation step: Compare the live page with the approved source material and credential records, then confirm that the attribution and review information are visible to the reader.

Internal-link and page-differentiation evidence

Trace internal links from navigation, service hubs, provider pages, and genuine location pages to the preferred service destinations. Record ambiguous anchor text, orphaned pages, and cases where several destinations appear to answer the same patient need. This check is about information architecture and page purpose, not a guarantee that changing links will alter rankings.

Evidence required: Source page, destination page, anchor wording, crawl path, and the intended patient journey between those assets.

Severity: High when important service information is orphaned or several pages create conflicting preferred destinations. Medium when the path is merely unclear but still usable.

Owner: SEO and editorial own internal-link decisions; site owners confirm navigation constraints and the correct destination for each patient need.

Corrective action: Point relevant links to the preferred page, remove unnecessary competing paths, and use descriptive anchor wording that matches the destination without stuffing keywords.

Validation step: Re-crawl the affected pages and manually follow the revised paths to confirm that the intended destination is reachable and unambiguous.

Thin, duplicate, and competing-page evidence

Use a crawl and manual review to identify pages that repeat the same service explanation, differ only by superficial location wording, or provide too little useful information to justify a separate search landing page. The source uses approximately 300 words as an internal screening trigger for manual review, not as a Google quality rule. A shorter page can be sufficient when it fully answers its purpose, and a longer page can still be weak if it is repetitive or inaccurate.

Evidence required: Candidate page set, similarity notes, page purpose, index status, and the specific patient information each page contributes that another page does not.

Severity: High when duplicate or conflicting pages obscure the correct service or location destination. Medium when the issue is mainly redundant copy or weak usefulness without a clear indexing conflict.

Owner: SEO and editorial jointly decide whether to consolidate, rewrite, redirect, or retain pages; operations confirms location reality; clinical reviewers confirm medical statements after consolidation.

Corrective action: Consolidate pages that serve the same purpose, expand only where distinct patient information is missing, and keep a dedicated location page only for a genuine office with useful location-specific information.

Validation step: Re-crawl the affected set, confirm the preferred destination is internally linked and indexable as intended, and manually verify that each remaining page has a distinct patient-facing purpose.

This stage identifies questions that SEO staff should not decide alone. The purpose is to document patient-data flows, advertising language, testimonial practices, and other sensitive publishing choices so the responsible reviewer can evaluate them against the practice's actual jurisdiction, contracts, policies, and clinical context. This content cannot guarantee compliance, and responsible legal, medical, or regulatory reviewers remain required.

Patient-contact and data-flow evidence

Inventory appointment requests, intake forms, refill requests, chat tools, call systems, analytics tags, embedded schedulers, and third-party widgets that can receive patient or prospective-patient information. For each one, record what information is requested, where it is transmitted, where it is stored, who can access it, and which vendor agreements or practice policies govern the flow. Do not label a tool HIPAA-compliant solely because a vendor markets it that way or because the site uses encryption.

Evidence required: Form fields, data destination, vendor name, configuration screenshots, relevant agreements available to the practice, and the internal owner who can explain the workflow.

Severity: Critical when the practice cannot account for sensitive information handling or when a patient-facing tool visibly sends information to an unintended destination. High when required review evidence is missing. Lower severity applies to documentation gaps that do not indicate an actual data-flow problem.

Owner: Technical owners document configuration; practice privacy or compliance personnel and counsel determine obligations; clinical leadership confirms what information is necessary for the patient workflow.

Corrective action: Reduce unnecessary data collection, correct misrouted or insecure workflows, obtain the appropriate review of vendor and agreement requirements, or replace the tool when the responsible reviewer determines the current setup is unacceptable.

Validation step: Re-test the full patient-facing flow and confirm the documented destination, access controls, and approved configuration match the post-fix state.

Advertising, credential, and health-claim evidence

Review service pages, provider bios, metadata, promotional copy, local-profile text, testimonials, endorsements, fees, comparisons, specialty language, and before-and-after material. Capture the exact statement and its context. The audit should flag unsupported absolutes, outcome promises, ambiguous credentials, or claims whose substantiation cannot be located, then route them for the required legal, medical, or regulatory decision.

Evidence required: Exact published wording, page or profile location, supporting source or credential record where one exists, applicable internal policy, and reviewer disposition.

Severity: Critical for a materially misleading health or credential claim or a statement the responsible reviewer identifies as prohibited. High when support or approval is missing for an important claim. Medium for wording that is accurate in substance but unclear or insufficiently qualified.

Owner: Editorial staff can identify and revise language, but legal, regulatory, credentialing, or qualified medical reviewers decide whether the claim is acceptable for the practice.

Corrective action: Remove, qualify, substantiate, or replace the flagged statement according to reviewer direction. Do not use search demand as a reason to retain language the practice cannot support.

Validation step: Compare the live page with the approved wording and source record, then archive the review decision so future updates do not silently reintroduce the issue.

Review-solicitation and public-response evidence

Map how the practice asks for reviews, who receives requests, whether any incentive is offered, what happens after negative feedback, and how staff respond publicly. The safe operating principle for this audit is consistent requests for honest feedback from eligible patients without incentives, discouraging negative feedback, or selecting only satisfied patients. Public replies should avoid confirming sensitive patient details and should follow the practice's approved communications process.

Evidence required: Request message, recipient-selection rule, automation logic, incentive policy, escalation path, and representative public responses.

Severity: Critical if the workflow gates reviewers, suppresses negative feedback, discloses sensitive patient information, or uses an incentive the responsible reviewer does not approve. High when the selection logic or response policy is undocumented.

Owner: Practice operations owns the workflow; marketing owns message execution; privacy, compliance, or legal reviewers own policy questions.

Corrective action: Remove selective routing or unapproved incentives, standardize the request to eligible patients, and replace risky public-response templates with language approved by the practice.

Validation step: Run a test through the current workflow, verify recipient logic and message content, and review recent public responses for consistency with the approved process.

The audit is complete only when observations become decisions. Build a working register that ties each issue to the original evidence, affected asset, severity, accountable owner, correction, validation source, and current status. Keep speculative ideas separate from confirmed defects so the team does not spend equal effort on everything that appears in a tool export.

How to prioritize findings without overclaiming impact

Move first on conditions that block access, misstate office information, break patient-contact paths, or require urgent compliance review. Next, address defects on important service and location pages where the evidence shows a real access, accuracy, or relevance gap. Schedule lower-risk improvements such as clearer attribution, stronger internal navigation, or secondary citation cleanup after the core record is stable. A priority label is an operating decision, not a prediction of traffic or appointment gains.

Evidence required: Every prioritized item must link back to the observation that justified it. Include the affected page or profile, the source of evidence, the reason for severity, and any dependency that must be resolved first.

Severity: Preserve the same severity definitions used in earlier stages so a critical technical blocker is not diluted by a large number of low-risk editorial tasks.

Owner: Assign one accountable owner per finding even when several people contribute. Shared ownership without a named decision-maker makes validation and closure difficult.

Corrective action: Write an acceptance condition before work begins. The task should state what will change and what evidence will count as successful completion.

Validation step: After the change is live, return to the original evidence source and record the result. If the condition persists, reopen the finding or revise the diagnosis instead of declaring success because the task was shipped.

When the self-audit should escalate

Escalate when the team can reproduce a problem but cannot identify a safe correction, when visibility changes are broad and unexplained, when page templates or indexing rules interact in ways the practice cannot confidently diagnose, or when legal, medical, privacy, or regulatory questions remain unresolved. Outside help should begin with the evidence already collected rather than restarting with a generic checklist.

If visible fixes have been completed and the practice is using an observation window of 60 to 90 days to assess whether Search Console coverage or query patterns change, treat that window as a measurement stage rather than a guarantee. Search behavior, crawling, competition, and site history can make the outcome earlier, later, or inconclusive. The decision to escalate should rest on the quality of the evidence and the cost of unresolved uncertainty, not on a promised deadline.