Run SEO as a verifiable release checklist

Use this section as the release gate for the parts of a freelance web designer site that search engines and prospective clients must be able to access reliably. The purpose is not to chase a score. It is to document whether important portfolio and service pages render, load, link, and describe the business consistently.

Check: verify loading and layout behavior on the pages that introduce your services and strongest work. Evidence required: a PageSpeed Insights report or equivalent test, available field data, a browser network trace, and a short screen recording from a representative mobile device.

Pass condition: the main service or portfolio content becomes usable without a reproducible loading defect, and the largest visible element does not create avoidable delay. The existing source uses an LCP reference of 2.5 seconds; treat that as a performance reference to investigate, not as a guaranteed ranking threshold.

Fail condition: an oversized hero, script bundle, font dependency, or layout shift repeatedly prevents a visitor from seeing or using the primary content under the tested conditions. Severity: high when the defect affects the homepage, primary services, or a major portfolio entry; medium when it is confined to noncritical supporting content.

Owner: the person responsible for front-end delivery. Corrective action: right-size visual assets, reserve layout space, delay nonessential scripts, preload only resources that are actually critical, and remove effects whose cost is greater than their value to the visitor.

Validation step: rerun the same test on the same page and record the before-and-after evidence rather than substituting a different page or device.

Check: verify that structured data accurately describes what is already visible and true on the site. Evidence required: the rendered markup, the visible business information, and validation output from an appropriate structured-data testing tool.

Pass condition: the markup is syntactically valid, matches the visible page, and contains only properties that can be supported by public business information. It should describe the entity or content; it should not be added because someone expects a special search treatment.

Fail condition: business details conflict with the page, unsupported properties are inserted, or markup is used to imply services, locations, prices, ratings, or credentials that are not substantiated.

Severity: high for inaccurate entity claims; medium for invalid but nonmisleading markup. Owner: developer or technical SEO owner. Corrective action: remove unsupported properties, correct the source-of-truth business information, and keep only markup that faithfully describes the page. Validation step: validate the rendered page again and compare every material property with the visible content.

Check: verify that portfolio media is efficient at the dimensions in which it is actually shown. Evidence required: the transferred file sizes, source and rendered dimensions, responsive image configuration, and visual QA on the devices that matter to the business.

Pass condition: the production page does not ship materially oversized assets for the displayed context and the optimized output preserves the intended presentation. A previously published source example cited reductions of 30-50% when changing image delivery; treat that range as an observation to test on your own assets, not as a promised saving.

Fail condition: full-resolution source files are sent where smaller responsive variants would preserve the same visible quality, or compression introduces artifacts that weaken the work. Severity: high on image-heavy landing pages; medium on secondary gallery pages.

Owner: designer and front-end implementer jointly. Corrective action: export efficient variants, configure responsive sources, lazy-load noncritical media, and keep archival masters outside the production payload. Validation step: compare transferred bytes and visual fidelity before and after the change under the same conditions.

Check: verify that maintained internal links reach intentional live destinations. Evidence required: a full crawl, a manual pass through navigation and case-study links, and search console error reporting where available.

Pass condition: important internal links resolve to the intended live page, and removed resources have a deliberate handling decision. Fail condition: active navigation, service content, portfolio cards, or maintained articles lead a visitor to a 404 response without a deliberate reason.

Severity: high when the broken path is part of a commercial journey; medium for an isolated supporting reference. Owner: site maintainer. Corrective action: restore the intended destination, update the source link, or redirect a moved resource to its closest relevant replacement.

Do not send unrelated removed pages to the homepage merely to eliminate an error code. Validation step: recrawl the affected paths and manually follow the corrected journey from the original linking page.

Use this section to decide whether a prospect can understand the services, specialization, and proof behind the visual work. Search visibility is useful only when the landing page gives the visitor enough information to evaluate fit.

Check: give each genuinely distinct service or specialization a page that supports a buying decision. Evidence required: the actual service inventory, current navigation, inquiry language, search query data where available, and examples of how clients distinguish the work during sales conversations.

Pass condition: a prospective client can find a page that explains who the service is for, what is included, the boundaries of the work, how the engagement is approached, and which portfolio examples support the positioning.

Fail condition: materially different services are collapsed into a visual list with little context, or thin pages are created only to repeat near-identical keyword phrases. Severity: high when the missing page corresponds to a core revenue service; medium when the overlap can be resolved by consolidating existing content.

Owner: the freelancer or the person responsible for positioning and site copy. Corrective action: create, merge, or rewrite pages around real service differences and buyer questions. Do not manufacture separate pages for distinctions the business does not actually make.

Validation step: ask whether a qualified prospect could compare the service with an alternative without needing a call just to understand the basics, then verify that the page is linked from relevant navigation or content.

Check: turn major portfolio entries into factual case studies rather than image-only galleries. Evidence required: client-approved project facts, the designer's role, scope, constraints, deliverables, and any outcome evidence the client permits the designer to publish.

Pass condition: the page explains the problem, the work performed, the reasoning that is safe to share, and why the project is relevant to a similar prospect. The source used 500 words as an editorial prompt; use it only as a drafting reference, not as a ranking requirement.

Fail condition: the page contains attractive visuals but too little text for a prospect to understand the assignment, the designer's contribution, or the relevance of the work. Severity: high for flagship work used to support a core service.

Owner: designer or content owner. Corrective action: add a concise project narrative based on substantiated facts. A previously published example cited a 20-40% conversion change; do not repeat that result unless the specific project has measurement evidence and permission to publish it.

Validation step: verify every outcome statement against project records and confirm that the case study links naturally to the service it demonstrates.

Check: write alternative text according to the purpose of the image in context. Evidence required: an image inventory, rendered page context, and an accessibility review of meaningful visuals. Pass condition: informative images have concise alternative text that communicates what a nonvisual user needs from the image, while decorative images are handled as decorative.

Fail condition: alternative text is absent where meaning would be lost, duplicated across unrelated images, stuffed with search phrases, or copied mechanically from a filename such as image1.jpg. Severity: medium for isolated misses; high when key explanatory images lose meaning without text alternatives.

Owner: content owner with accessibility review. Corrective action: rewrite the text around the image's function, not around a keyword target. Validation step: test the page with images unavailable or with an accessibility workflow and confirm that the intended information remains understandable.

Check: connect services and proof with useful internal links. Evidence required: a crawl graph, page templates, and a manual review of journeys from service pages to relevant case studies and back. Pass condition: related case studies and service pages link to one another where the relationship helps the reader continue evaluating the work, and anchor text describes the destination naturally.

Fail condition: important proof pages are isolated, the only path depends on a visual interaction that is difficult to crawl or use, or repeated exact-match anchor text is inserted without editorial purpose.

Severity: high for isolated core pages; medium for weaker supporting paths. Owner: site architecture or content owner. Corrective action: add contextual links where they clarify the relationship between a service, an example, and the next decision step.

Validation step: recrawl the site and manually follow a complete path from discovery to service detail, proof, and contact.

Use this section only where local discovery and third-party business information reflect the freelancer's real operations. The goal is accurate representation, not manufacturing geographic signals.

Check: maintain a Google Business Profile only when the business is eligible and the information is accurate. Evidence required: the real business name, operating address or service-area basis where applicable, category selection, contact details, hours or availability information, and the corresponding information on the website.

Pass condition: the profile represents the actual business, follows platform rules, and agrees with the site's public business facts. Fail condition: the profile contains invented locations, duplicate representations, misleading categories, stale contact information, or service areas that imply an operating presence the freelancer does not have.

Severity: high for misleading business information; medium for stale but nondeceptive details. Owner: business owner. Corrective action: correct the source-of-truth business information and the profile.

Treat profile content as communication with prospective clients, not as a guaranteed or official ranking tactic. Validation step: compare the live profile field by field with the current website and business records.

Check: request reviews consistently without gating or keyword scripting. Evidence required: the request template, eligibility rule, sending process, and a sample of published responses. Pass condition: eligible clients are asked for honest feedback under the same rule regardless of expected sentiment, without incentives, discouraging negative feedback, or selecting only satisfied clients.

Responses should address the reviewer naturally rather than inserting target phrases for search purposes. Fail condition: the process screens for positive sentiment, offers compensation, suppresses critical feedback, or pressures clients to mention specific services or keywords.

Severity: high because the issue affects trust and platform compliance. Owner: business owner or client-success owner. Corrective action: replace selective requests with a neutral process and document when a project becomes eligible for an ask.

Validation step: sample recent requests and confirm the same policy was applied regardless of the client's likely sentiment.

Check: keep legitimate directory and citation data accurate. Evidence required: an inventory of maintained profiles or directories, the current business record, and a reason each listing is relevant to the freelancer's professional presence.

Pass condition: maintained listings accurately represent the business and the same source-of-truth details are used. The source used 100% consistency as a hygiene target; treat that as an internal data-quality objective rather than an official ranking threshold.

Fail condition: active listings conflict on material business facts, use fabricated locations, or exist only as low-value placements with no legitimate directory purpose. Severity: medium for inconsistent but honest data; high for misleading business representations.

Owner: business owner or local-search owner. Corrective action: fix useful listings and stop maintaining placements that do not accurately or meaningfully represent the business. Validation step: compare the maintained listings with the current business record after corrections are published.

Check: publish a location page only when the location is genuine and the page can contain useful local information. Evidence required: proof of the actual location or operating presence, the services genuinely available there, and information that a prospective client in that market would find materially useful.

Pass condition: the page accurately describes how the freelancer serves that location and contains distinct information beyond a swapped place name. Fail condition: the page is a duplicate template created only to target a nearby market, or it implies an office, team, or presence that does not exist.

Severity: high when the page could mislead a prospective client; medium when the problem is simply thin duplication. Owner: business owner and content owner. Corrective action: consolidate unsupported market pages and explain remote or regional service honestly where that is the real model.

Validation step: compare every location claim with the actual business footprint and read the page as a local prospect deciding whether the information is genuinely specific.

Use this section to review trust-sensitive claims before they become search copy. A freelance web designer can demonstrate knowledge of regulated or standards-driven work, but public language should match the actual role, evidence, and limits of the service.

Check: make accessibility claims precise and supportable. Evidence required: design and development process documentation, testing evidence, issue logs, and examples of deliverables the freelancer can substantiate.

Pass condition: public copy distinguishes standards, testing, remediation, and implementation responsibilities. If WCAG 2.1 is referenced, the page states what was evaluated or targeted rather than implying blanket legal compliance.

Fail condition: accessibility language is used as a generic trust badge, a ranking phrase, or an absolute legal promise without evidence of process and scope. Severity: high when accessibility is sold as part of the service; medium when the statement is merely vague.

Owner: designer or accessibility lead, with qualified review where the claim has legal implications. Corrective action: replace broad compliance language with a specific description of what the freelancer can design, test, document, or coordinate. Validation step: compare the published claim with the actual testing process and project documentation.

Check: use healthcare privacy terminology only when the freelancer can explain the actual delivery boundary. Evidence required: service scope, hosting and form architecture, data flows the freelancer controls, contractual responsibilities, and client requirements where relevant.

Pass condition: the page distinguishes visual design and front-end implementation from hosting, storage, integrations, forms, and other components that may carry separate privacy or security obligations.

Fail condition: a broad healthcare compliance statement is used to target a niche even though the freelancer cannot substantiate the operational responsibility behind it. Severity: high for unsupported compliance claims.

Owner: business owner, with technical or legal review where appropriate. Corrective action: narrow the wording to the freelancer's actual role and remove claims that depend on systems or obligations outside that role. Validation step: trace each public claim to a documented responsibility in the delivery process.

Check: review professional advertising constraints before publishing niche-specific claims for attorney websites. Evidence required: the client's applicable rules, approved messaging, source material for professional-status claims, and a documented person responsible for final review.

Pass condition: the designer's own marketing describes relevant design experience without guaranteeing legal compliance or inventing claims about a client's specialization, outcomes, or credentials. Fail condition: legal-industry terminology is inserted as generic SEO copy without confirming that it is accurate, permitted, and appropriate to the client's jurisdiction or professional rules.

Severity: high when the claim could misrepresent a regulated professional service. Owner: business owner, with client or qualified legal review where needed. Corrective action: remove unsupported claims, separate design expertise from the client's legal advertising obligations, and document who approves sensitive copy.

Validation step: recheck the published language against the approved source material before release and after any substantive update.

Quick win: reduce the heaviest portfolio assets that a network trace shows are unnecessary at their displayed size. Evidence required: the current transferred bytes and a visual comparison after optimization.

Pass when the lighter file preserves the intended presentation; fail when the page still ships unnecessary source weight or the optimized asset visibly degrades. Severity: high on a primary entry page.

Owner: designer and front-end implementer. Corrective action: export responsive variants and replace the oversized source. Validation: repeat the same page load test. Planning allowance: 30 minutes.

Quick win: review the Google Business Profile and replace outdated media with 5 current project photos only if the profile is eligible and the images accurately represent the business. Evidence required: current profile media and the new approved assets.

Pass when the public media is current and truthful; fail when it is stale, misleading, or unrelated. Severity: medium. Owner: business owner. Corrective action: update the media without treating profile activity as a ranking guarantee. Validation: inspect the live profile after publication. Planning allowance: 15 minutes.

Quick win: fix broken internal links found in the latest crawl. Evidence required: crawl output and the intended destination for each maintained link. Pass when the affected links resolve to the correct live resource; fail when a maintained journey ends at an unintended missing page.

Severity: high for commercial paths. Owner: site maintainer. Corrective action: update the source link or map a genuinely moved resource to its closest replacement. Validation: recrawl the changed pages. Planning allowance: 1 hour.

Quick win: improve the contact call to action on the top 3 decision-support pages where analytics shows relevant organic entry traffic. Evidence required: landing-page data, current CTA placement, and the actual contact path.

Pass when the CTA states a clear next step and reaches a working contact method; fail when the next action is ambiguous, hidden, or broken. Severity: high for conversion clarity. Owner: designer or site owner.

Corrective action: simplify the next step without adding unsupported urgency or outcome claims. Validation: test the complete contact journey on mobile and desktop. Planning allowance: 20 minutes.

• Visual-first pages without explanatory text. Evidence required: the rendered page, query data, and the service or project information a prospect needs. Pass when a visitor can understand the offer and relevance without interpreting imagery alone; fail when critical context exists only in visuals. Severity: high on service pages. Owner: content owner. Corrective action: add concise factual context around the work. Validation: review the rendered text and the queries that lead to the page.
• Mobile QA treated as secondary. A previously published internal estimate placed initial discovery traffic in the 40-60% range. No supporting source URL is present here, so keep that figure marked for source reconciliation rather than presenting it as a verified benchmark. Evidence required: actual device analytics, field data, and manual mobile testing. Pass when the portfolio is usable and persuasive on devices represented in real traffic; fail when navigation, media, forms, or copy break under those conditions. Severity: high when contact or service evaluation is affected. Owner: designer and front-end implementer. Corrective action: fix confirmed mobile defects. Validation: retest the same devices and journeys.
• Generic page titles. Evidence required: the title metadata, visible heading, and purpose of each important page. Pass when the title describes the page clearly and distinguishes it from other pages; fail when important pages use vague labels that do not communicate their purpose. Severity: medium. Owner: content owner. Corrective action: rewrite for clarity rather than keyword repetition. Validation: inspect the rendered metadata after deployment.
• Stale facts mistaken for a freshness problem. Evidence required: service details, links, claims, portfolio facts, and dated references that may have changed. Pass when maintained pages remain accurate and useful; fail when public information is obsolete or broken. Severity: medium for outdated commercial facts. Owner: site maintainer. Corrective action: update content when the underlying fact changes and retire obsolete material appropriately. Validation: use a recurring factual review tied to business changes, not an arbitrary publishing cadence.