The 2026 Burn Surgeon SEO Checklist for Verifiable Medical Authority

Use this section to verify the technical conditions that affect safe data handling, crawl access, page usability, and truthful machine-readable information. Do not mark a checkpoint passed because a tool reports a green score; retain evidence that a responsible owner reviewed the underlying configuration and public behavior.

Checkpoint: Encrypted transport and inquiry-data flow. Evidence required: a crawl showing secure page and asset delivery, an inventory of every inquiry or intake field, the destination system for submitted data, vendor agreements or other privacy documentation required by the organization's reviewers, and access-control records.

Pass condition: no intended public page or submission path downgrades to insecure transport, and the designated privacy/security reviewer has approved the documented data flow for its actual use. Fail condition: insecure delivery, unknown destinations, unnecessary collection, uncontrolled access, or missing required review.

Severity: Critical where patient or prospective-patient information could be exposed; otherwise High. Owner: security/privacy lead with web engineering and the form-system administrator. Corrective action: remove unnecessary fields, correct insecure requests, restrict access, update the data-flow record, and route vendor or contract issues to the responsible reviewer.

Validation step: recrawl the affected paths, submit a controlled test with non-sensitive test data, verify the destination and permissions, and record reviewer sign-off. Tools: Qualys SSL Labs, Screaming Frog.

Checkpoint: Mobile performance and layout stability. Evidence required: representative mobile performance reports, field data when available, template-level findings, and manual testing on pages used to find clinicians, contact the program, or understand care.

Pass condition: priority pages render usable content without blocking errors or disruptive layout movement, and any performance targets are documented as internal operating goals rather than guarantees.

Fail condition: slow or unstable templates materially obstruct reading, navigation, or contact actions. Severity: High on access-critical pages and Medium elsewhere. Owner: web engineering with product or content operations.

Corrective action: reduce avoidable script and media cost, reserve space for late-loading elements, optimize critical assets, and retest the affected template. Validation step: compare before-and-after mobile results and manually confirm the corrected page on a constrained connection. Tools: Google PageSpeed Insights, Search Console.

Checkpoint: Accurate MedicalOrganization and Physician structured data. Evidence required: rendered markup, the corresponding visible page facts, the internal source for names, affiliations, specialties, and credentials, plus syntax validation.

Pass condition: markup is syntactically valid, matches visible content, and does not state qualifications or services that the organization cannot substantiate. Fail condition: hidden-only claims, stale affiliations, unsupported credentials, duplicate entities that create ambiguity, or invalid markup.

Severity: Medium unless the markup repeats a materially misleading medical or identity claim, which is High. Owner: technical SEO or web engineering with credential verification by the appropriate clinical or medical-staff owner.

Corrective action: remove unsupported properties, align entity facts with the page, and correct syntax. Validation step: compare markup line by line with the rendered page and authoritative internal records, then retest.

Tools: Schema.org, Google Rich Results Test. Structured data does not by itself guarantee rankings, rich results, or AI inclusion.

Checkpoint: Lead capture appropriate to the organization's HIPAA obligations. Evidence required: form-field inventory, system architecture, retention and access rules, vendor documentation, and a determination by the organization's responsible privacy/legal reviewer about which HIPAA requirements apply to the specific workflow.

Pass condition: the implemented collection and handling match that reviewed determination and the public form does not request more information than the workflow needs. Fail condition: the team cannot explain where data goes, who can access it, how long it is retained, or which reviewed requirement governs it.

Severity: Critical for exposed sensitive information; otherwise High. Owner: privacy/legal, security, and the operational owner of intake. Corrective action: minimize collection, change routing or permissions, update vendor arrangements as required by the responsible reviewer, and revise the form copy to set accurate expectations.

Validation step: run an end-to-end test with non-sensitive test data and document approval of the final flow. Tools: Jotform HIPAA, Formstack. Tool branding alone is not evidence that a particular implementation meets legal obligations.

Checkpoint: Accessibility review using WCAG 2.1 as the existing benchmark in this source. Evidence required: automated scan results, keyboard-only review, screen-reader checks on key flows, text alternatives, focus behavior, form labels and error handling, plus any organization-specific accessibility requirements approved by counsel or accessibility leadership.

Pass condition: high-priority barriers found in the tested flows are resolved or have an approved remediation plan, and the team does not equate a single scanner score with legal compliance. Fail condition: a user cannot reliably navigate, understand, or submit a key public flow with supported assistive methods.

Severity: High for access-blocking barriers and Medium for less consequential defects. Owner: accessibility lead with design and engineering. Corrective action: remediate the defect at the component or template level where possible and update the regression test.

Validation step: repeat both automated and manual checks on the corrected experience. Tools: Axe DevTools, WAVE Evaluation Tool.

For YMYL medical content, authority should be demonstrable rather than asserted. Use these checks to confirm that readers can identify who wrote or reviewed the information, why that person is qualified to address it, which facts are supported, and which affiliations are current.

Google's Search Quality Rater Guidelines can inform quality review, but E-E-A-T is not a single markup field or a guaranteed ranking formula.

Checkpoint: Surgeon biography with verified credentials. Evidence required: current internal CV, medical-staff record or other authoritative credential source, dates of verification, and the public biography.

Pass condition: every displayed certification, training claim, title, affiliation, and clinical focus matches the authoritative record and the page distinguishes factual credentials from marketing language.

Fail condition: expired, ambiguous, unsupported, or inconsistent credential claims. Severity: High because inaccurate credentials can mislead readers. Owner: medical-staff or credentialing owner with the web content lead.

Corrective action: correct or remove unsupported statements, add the verification date to the editorial record, and update dependent pages that repeat the same claim. Validation step: a second reviewer compares the final page with the authoritative record. Tools: Internal CVs, Board Certification Databases.

Checkpoint: Research and publication references. Evidence required: a publication list matched to the correct clinician, source records for each cited work, and a check that links or citations support the adjacent claim.

Pass condition: publications are correctly attributed, relevant to the stated topic, and described without implying that publication history proves a clinical outcome. Fail condition: misattribution, broken identity matching, unrelated citations used as authority decoration, or unsupported conclusions.

Severity: Medium, rising to High if the error changes a medical claim. Owner: clinician author or research administrator with editorial review. Corrective action: correct attribution, remove irrelevant references, and rewrite any overbroad claim.

Validation step: verify a sample against Google Scholar, PubMed, or the original publication record and confirm author identity. Tools: Google Scholar, PubMed.

Checkpoint: Named authorship and medical review workflow. Evidence required: author name, reviewer name when review is required, role and qualification pages, source list, review date, change log, and documented criteria for when content must return to medical review.

Pass condition: readers can identify accountable contributors and the internal record shows that substantive medical changes received the required review. Fail condition: anonymous medical advice, decorative 'Fact Checked By' language without a real review record, or stale review labels that do not reflect the current text.

Severity: High for pages that could influence care decisions; Medium for lower-risk institutional content. Owner: medical editor with designated clinical reviewers. Corrective action: assign qualified contributors, complete the review, update attribution, and archive the evidence.

Validation step: audit the page against the editorial record and confirm that the displayed review date matches the completed review. Tools: Internal Editorial Policy.

Checkpoint: Earned medical and institutional link quality. Evidence required: referring-page list, context for how each material link was earned, destination page, and screening for paid, exchanged, deceptive, or irrelevant placement.

Pass condition: outreach and earned links are editorially defensible, relevant, and not represented internally as guaranteed ranking drivers. Fail condition: link schemes, misleading sponsorship, fabricated endorsements, or outreach that asks an institution to state something it cannot verify.

Severity: High for manipulative or misleading practices and Medium for routine low-quality links. Owner: SEO lead with communications or compliance review where endorsements are involved. Corrective action: stop the practice, remove or disavow only when appropriate to the actual issue, and replace the tactic with legitimate resource, research, or affiliation outreach.

Validation step: review a sample of referring pages and the outreach record. Tools: Ahrefs, Semrush. Relevant sources may include university medical centers (.edu), health departments (.gov), and professional associations such as the American Burn Association, but domain suffix alone does not establish quality.

Checkpoint: Hospital affiliations and designation terminology. Evidence required: current affiliation documentation, the institution's approved naming convention, and the public page where the relationship is stated.

Pass condition: the affiliation and designation wording exactly match verified records and do not imply a level, status, or scope that has not been confirmed. Fail condition: stale affiliations, ambiguous relationships, or unsupported designation language.

Severity: High because patients and referrers may rely on institutional status. Owner: hospital relations or medical-staff office with clinical leadership and web content. Corrective action: reconcile the wording with the authoritative record and remove unsupported status claims.

Validation step: obtain responsible-owner confirmation and check every repeated occurrence on the site. Tools: Google Business Profile. Source reconciliation note: the existing phrase 'Level 1 Burn Centers' should not be published as a designation unless the responsible reviewer confirms that exact terminology for the institution being described.

Content should help different audiences understand what the organization does, when a page is informational rather than diagnostic, and how to reach an appropriate care channel. Separate acute injury information from later reconstructive concerns when the questions and pathways differ, but do not create thin pages merely to capture variations of a keyword.

Checkpoint: Burn-type educational coverage. Evidence required: content inventory for thermal, chemical, electrical, and radiation burn topics; clinician-approved scope; source list; and internal links to the appropriate care or emergency guidance.

Pass condition: each published topic explains its scope accurately, identifies when urgent professional evaluation may be needed without attempting remote diagnosis, and is reviewed by a qualified clinician.

Fail condition: unsupported treatment instructions, missing escalation guidance where clinically necessary, duplicated pages with trivial differences, or content outside the program's real expertise.

Severity: High for unsafe or misleading medical guidance and Medium for coverage gaps. Owner: clinical content lead with a burn-care reviewer. Corrective action: correct medical statements, merge redundant pages, add appropriate care-pathway guidance, and complete review.

Validation step: clinician re-review plus an editorial check that the page's title, headings, and internal links match its actual scope. Tools: Keyword Research Tools, Medical Textbooks.

Checkpoint: Reconstructive and scar-care service pages. Evidence required: service-line confirmation, clinician-reviewed description of candidacy and limits, search-query evidence showing distinct user questions, and a page inventory to prevent overlap.

Pass condition: pages for topics such as 'scar contracture surgery', 'skin graft types', and 'laser scar revision' are published only when they accurately reflect the program's services or educational remit and clearly distinguish education from individualized medical advice.

Fail condition: the page implies availability, candidacy, outcomes, or expertise that cannot be substantiated, or competes with a near-duplicate page. Severity: High for misleading service or outcome claims and Medium for duplication.

Owner: service-line lead with medical editor and SEO strategist. Corrective action: correct the service description, consolidate overlapping pages, and align internal anchors with the reader's actual task.

Validation step: compare the final page with approved service documentation and review search-query overlap. For specialized planning, use the existing natural anchor wording that points readers to the burn surgeons industry page. Tools: Google Keyword Planner.

Checkpoint: Case studies and before/after materials. Evidence required: documented permission for the specific public use, approved de-identification process where applicable, source asset record, date, clinical context, and reviewer approval of captions and outcome language.

Pass condition: the organization can demonstrate permission and approved handling, the material is not misleadingly edited or selectively framed, and captions avoid implying typical or guaranteed results.

Fail condition: uncertain permission, identifying details outside approved scope, unsupported outcome language, or a gallery that lacks necessary context. Severity: Critical for unauthorized disclosure and High for misleading outcome presentation.

Owner: privacy/legal and clinical marketing with the treating or reviewing clinician as appropriate. Corrective action: unpublish questionable material, resolve consent and usage scope with responsible reviewers, correct captions, and restore only after approval.

Validation step: compare each live asset with the consent and approval record. Tools: Patient Consent Forms, Professional Photography.

Checkpoint: Post-operative and wound-care education. Evidence required: clinician-approved instructions, source references, date of last medical review, and a clear statement of the content's intended educational scope.

Pass condition: content about topics such as caring for a skin graft or managing hypertrophic scars is consistent with the organization's approved guidance, makes clear when readers should contact their care team, and avoids individualized treatment directions that the page cannot safely provide.

Fail condition: conflicting instructions, stale protocols, missing escalation cues, or advice presented as universally applicable. Severity: High. Owner: clinical education or nursing lead with medical editorial oversight.

Corrective action: reconcile the page with current approved guidance, narrow the scope where needed, and complete medical review. Validation step: compare the published instructions with the approved internal source and record the reviewer and review date. Tools: Internal Nursing Protocols.

Checkpoint: Natural-language question coverage. Evidence required: Search Console queries or other research showing recurring reader questions, a content map showing where each question is answered, and clinical review for answers that could affect care decisions.

Pass condition: relevant questions are answered directly in ordinary language, within the page that best matches the intent, without keyword stuffing or unsupported certainty. Fail condition: answers are evasive, medically overbroad, duplicated across many pages, or written solely to mimic a search feature.

Severity: High for unsafe medical answers and Medium for search-quality issues. Owner: SEO/content lead with clinical reviewer. Corrective action: rewrite for scope and clarity, consolidate duplicate answers, and add sources or escalation language when needed.

Validation step: compare the answer with its source and confirm that the page still serves the underlying reader question. Tools: AnswerThePublic, AlsoAsked. FAQ content can be useful for readers, but FAQPage markup should not be added under this contract, and Google no longer shows FAQ rich results, so the checklist does not treat FAQ markup as a search-feature opportunity.

Local search work for burn surgery should begin with factual access information, not with tactics that imply every service area deserves a page or that profile activity guarantees visibility. Verify genuine patient-facing locations, referral relationships, and public contact routes before optimizing them.

Checkpoint: Google Business Profile accuracy for eligible patient-facing locations. Evidence required: authoritative name, address, phone, category, hours, website destination, location eligibility determination, and an operations-approved statement of how urgent or emergency needs should be handled.

Pass condition: the profile describes a genuine eligible location, matches the institution's current public access information, and does not advertise emergency availability that the location cannot provide.

Fail condition: duplicate or ineligible profiles, inaccurate hours or categories, mismatched contact details, or emergency language that could misdirect a patient. Severity: Critical for misleading emergency access information, otherwise High.

Owner: local search or digital operations with the location's operational leader. Corrective action: correct the profile, remove unsupported service or hour claims, and align the linked page with the same access information.

Validation step: compare the live profile with the authoritative location record and complete a manual test of the contact path. Tools: Google Business Profile Manager. Profile completeness is a sound operating practice, not a guarantee of local rankings.

Checkpoint: Healthcare directory citation accuracy. Evidence required: a list of material directory profiles, current NAP (Name, Address, Phone) data from the authoritative location record, and a change log for corrections.

Pass condition: material profiles such as Healthgrades, Vitals, and WebMD identify the correct clinician or organization and match the current contact information closely enough to avoid user confusion.

Fail condition: wrong phone numbers, old locations, duplicate identities, incorrect specialties, or profiles that cannot be tied to the correct entity. Severity: High when a patient could be misdirected and Medium for less consequential inconsistencies.

Owner: local search or provider-directory operations. Corrective action: submit corrections through the directory's supported process and document unresolved discrepancies. Validation step: recheck corrected profiles and compare them with the authoritative internal record.

Tools: BrightLocal, Whitespark. Consistency can reduce confusion; this checklist does not treat directory citations as a guaranteed ranking factor.

Checkpoint: Affiliated hospital and university referral links. Evidence required: current affiliation record, the hospital or university directory entry, the destination page on the program site, and outreach correspondence if a correction is requested.

Pass condition: the external directory accurately identifies the clinician or program and any link points to a relevant, current page that supports the stated affiliation. Fail condition: stale affiliations, wrong destinations, broken links, or outreach that asks the institution to publish an unverified endorsement.

Severity: High for identity or affiliation errors and Medium for broken navigation. Owner: hospital relations, provider-directory owner, or communications team. Corrective action: request a factual directory correction or destination update using the institution's normal process.

Validation step: verify the live directory record and follow the link through to the intended page. Tools: Email Outreach.

Checkpoint: Reviews, responses, and genuine location pages. Evidence required: review-request policy, response guidance approved for privacy considerations, a sample of recent responses, location-page inventory, and proof that each location page represents a genuine location with useful location-specific information.

Pass condition: if reviews are requested, eligible patients or caregivers are asked consistently for honest feedback without incentives, discouraging negative feedback, or selecting only satisfied people; responses do not confirm an individual's patient status; and each location page contains accurate, useful details unique to that real location.

Fail condition: review gating, incentives tied to sentiment, responses that disclose or confirm protected relationships, fabricated local content, or pages created for nominal service areas without meaningful local information.

Severity: Critical for privacy disclosure, High for deceptive review practices, and Medium for thin location content. Owner: patient experience or reputation lead with privacy review, plus local content ownership.

Corrective action: stop selective solicitation, revise response templates, remove or consolidate thin market pages, and update genuine location pages from authoritative records. Validation step: audit a representative set of requests, responses, and location pages against policy and source records. Tools: Reputation Management Platforms, Google Search Console.

Triage action: Correct Physician structured data on surgeon biography pages. Evidence required: rendered markup, visible biography facts, and authoritative credential records. Pass condition: the markup matches the visible page and verified identity information with no unsupported claims.

Fail condition: invalid syntax, stale identity facts, or properties that contradict the page. Severity: High when identity or medical qualifications are misstated; otherwise Medium. Owner: technical SEO or web engineering with credential verification.

Corrective action: remove unsupported properties and align markup with approved visible content. Validation step: retest syntax and compare the final markup with the rendered page and credential source.

Implementation stage estimate for a limited-scope correction: 1-2 hours. This is an operating estimate from the source, not a visibility guarantee.

Triage action: Update Google Business Profile facility photography. Evidence required: current approved images, rights or internal approval for public use, location match, and a live-profile review. Pass condition: images accurately depict the genuine location or program environment, contain no unintended patient information, and are approved for publication.

Fail condition: stale, misleading, unauthorized, or privacy-sensitive images. Severity: Medium, rising to High for privacy or material misrepresentation. Owner: local search or communications with privacy review when needed.

Corrective action: remove problematic images and upload approved current assets through the supported profile workflow. Validation step: inspect the live profile after publication and confirm that only approved assets are displayed.

Implementation stage estimate for prepared assets: 1 hour. Photography can improve user understanding; it is not presented here as a guaranteed click-through or ranking driver.

Triage action: Repair broken internal links to important care and clinician pages. Evidence required: crawl report, list of affected source pages, intended destinations, and a manual check of high-priority navigation paths.

Pass condition: internal links resolve to the intended current pages without broken hops or misleading anchor text. Fail condition: broken destinations, redirect loops, links to retired services, or anchors that misdescribe the target.

Severity: High for links that interfere with finding care or contact information; otherwise Medium. Owner: web content or engineering. Corrective action: update the destination, redirect only when the replacement is genuinely equivalent, and fix reusable templates where the defect repeats.

Validation step: recrawl the repaired paths and manually follow representative links. Implementation stage estimate for a contained batch: 2 hours.

• Acute and reconstructive intent is mixed together. Evidence required: query data, page inventory, service-line confirmation, and page-level intent mapping. Pass condition: acute injury information and later reconstructive or scar-care information are separated where reader needs and care pathways genuinely differ, with no thin duplication. Fail condition: one page tries to serve incompatible urgent and elective questions or multiple near-duplicate pages compete for the same intent. Severity: High when access guidance is confusing, otherwise Medium. Owner: SEO/content lead with clinical service-line review. Corrective action: clarify scope, consolidate duplicates, and create a distinct page only when there is enough unique, useful content. Validation step: re-map target queries and manually review navigation between the corrected pages.
• Clinical imagery is generic, misleading, or insufficiently governed. Evidence required: asset source, rights or approval record, privacy review where needed, and page context. Pass condition: images are accurate for the page, approved for use, and do not imply outcomes or services that cannot be substantiated. Fail condition: unrelated stock imagery is presented as clinical evidence, patient information appears outside approved scope, or captions overstate results. Severity: Critical for unauthorized disclosure, High for misleading clinical representation, otherwise Medium. Owner: clinical marketing with privacy and medical review. Corrective action: remove the asset, replace it with an approved and accurate alternative, and correct captions. Validation step: audit the final page against the asset record and approval documentation.
• Technical defects are treated as ranking problems instead of user and data-quality problems. Evidence required: crawl errors, indexability settings, redirect map, canonical review, security findings, and impacted user paths. Pass condition: important public pages are reachable, intended for indexing when appropriate, internally linked, and free of technical defects that block users or crawlers. Fail condition: broken paths, accidental blocking, contradictory canonical signals, or unresolved security issues. Severity: Critical for security or access failures, High for widespread crawl/index defects, otherwise Medium. Owner: web engineering with technical SEO. Corrective action: fix the underlying template, routing, or configuration issue and document the change rather than assuming a search penalty. Validation step: recrawl and manually verify the repaired path.
• Slow pages are accepted because they work on office networks. Evidence required: representative mobile tests, field data when available, page-weight breakdown, and manual testing under constrained conditions. Pass condition: priority pages remain readable and navigable under realistic mobile conditions and performance regressions are tracked. Fail condition: key content or contact actions are materially delayed or unstable for mobile users. Severity: High on access-critical paths and Medium elsewhere. Owner: engineering and performance owner. Corrective action: reduce avoidable asset and script cost, prioritize critical content, and prevent regressions at the template level. Validation step: repeat the same representative tests after deployment and compare results.