One page. A clearer purpose.

On-Page SEO Checklist

This on-page SEO checklist shows you how to choose keywords, write title tags and meta descriptions, organize headings, improve content, and optimize images and links. Work on one page at a time. Use the explanations and examples to make changes in your site editor, then check the published page. Notes are optional.

Free to useNo account neededSaved in your browser
A structured content page with clear heading levels and a highlighted link connecting related articles.
An editorial illustration
Your working checklist

Work through the checklist

Click a square to mark a task as Pass. Click again to undo. Use the result menu for a problem, a blocker or a task that does not apply. You do not need to enter notes.

23 checks

Choose Primary and Supporting Keywords

On-page keyword research connects a real search to the page you are building. Choose a main phrase for the page, identify useful supporting questions, and check what people expect to find. Use those terms to plan the answer, rather than repeating a phrase until a tool reports a particular density.

Choose one main keyword for the page

A primary keyword names the main search you want this page to satisfy.

Use this for: A page you are preparing or improving.

Choose a phrase your intended reader would use for the product, service, resource or question this page covers. For an existing page, filter Search Console’s Performance report to its URL and review relevant queries. One primary keyword gives your writing a focus; the page can still answer closely related searches.

Example

Illustrative choices: “boiler repair in Bristol” for a genuine local repair service; “boiler maintenance checklist” for a practical information resource.

  1. Name the page’s actual topic and audience.
  2. Choose a clear main search phrase that fits both.
  3. Keep the phrase available while writing the title, main heading and opening.
More help and optional notesHigh · Website owner

Before you begin: The page topic and intended audience.

PassThe chosen phrase matches the page’s actual topic, audience and useful result.
FailThe phrase targets an unrelated topic or a service/resource the page does not provide.

If it fails: Choose a phrase matching the actual page.

Retest: Compare the phrase with the finished answer.

Not applicable: The page is outside this public-search review.

Optional: a short note about the change. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Find related phrases and questions to answer

Supporting keywords identify the useful details readers need around the main topic.

Use this for: A page you are preparing or improving.

Collect related customer questions, relevant Search Console queries and useful subtopics from search results. Group terms needing the same explanation, then give each group a place in the outline. Use them naturally in headings and paragraphs. There is no required number of secondary keywords or need for a section per spelling variation.

Example

For a repair-service page, useful supporting topics could include leaking boilers, loss of pressure and the actual service area. Include only services the business really offers.

  1. List related questions and terms relevant to this page.
  2. Group terms that need the same explanation.
  3. Map each useful group to a section or example.
More help and optional notesHigh · Website owner

Before you begin: The main topic and real reader questions.

PassRelevant supporting topics have a useful place in the content.
FailThe plan omits necessary answers or adds unrelated phrases solely for keywords.

If it fails: Add missing answers; remove unrelated terms.

Retest: Review the section plan against reader questions.

Not applicable: The page is outside this public-search review.

Optional: a short note about the change. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Match the page to search intent

Search intent is what someone wants to learn, compare, find or do.

Use this for: Every content page being reviewed.

Search the main phrase in your audience’s language and market. Inspect useful results: are they guides, service pages, products, comparisons or tools? Choose a format that fulfills the task. Use results to understand expectations, not as copy to imitate. A sales pitch alone cannot satisfy a search for usable instructions.

Example

“What is a boiler pressure gauge?” calls for an explanation. “Boiler repair in Bristol” may call for a local service. Verify the actual results and your real offering before choosing the page.

  1. Search the main phrase and open relevant results.
  2. Identify the expected page type and answer.
  3. Build the page around that task and its necessary conditions.
More help and optional notesHigh · Editor

Before you begin: The intended visitor and actual offering.

PassThe page format and content fulfill the main search task.
FailThe page serves a different task or promises an unavailable answer or action.

If it fails: Match the page format to the search task.

Retest: Compare the finished page with that task.

Not applicable: Usually applies; every content page needs a clear purpose.

Optional: uRL, intended task and mismatch. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Write Title Tags, Meta Descriptions and Readable URLs

Title tags, meta descriptions and page addresses help readers recognize the page before they open it. Write them for the specific topic and search intent. Put meaningful words first, make each page distinguishable, and check the published output rather than relying only on an editor preview.

Write a specific SEO title using your main keyword

A specific title tag tells searchers which topic or service the page covers.

Use this for: Public HTML pages with a page title.

Open the SEO title field in your website editor. Use the main phrase naturally, plus an accurate distinction such as the real service area. Around 50–60 characters is a first-draft guide, not a Google limit. Preview and remove repetition. The title and visible H1 can differ, but should describe the same page.

Example

Illustrative title: “Boiler Repair in Bristol | Example Heating” tells the reader more than “Services.” Replace the example name and location with real details.

  1. Write a unique title naming the main topic naturally.
  2. Add a useful, accurate distinction rather than extra keyword variants.
  3. Save and inspect the published browser-tab title or title element.
More help and optional notesHigh · Editor

Before you begin: SEO title edit access; otherwise use Blocked.

PassThe title clearly names the main topic, matches the page and differs from unrelated page titles.
FailThe title is missing, misleading, generic or stuffed with repeated phrases.

If it fails: Replace vague or repetitive title wording.

Retest: Inspect the published title element.

Not applicable: A non-HTML resource handled by a different publishing process.

Optional: current title and proposed revision. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Write a page-specific meta description

A meta description summarizes the page and gives the right visitor a reason to open it.

Use this for: Priority public HTML pages intended for search visitors.

In the SEO description field, summarize the answer or service, add a specific benefit and suggest a relevant next step. Use the main topic naturally. Roughly 140–160 characters is a draft guide, not a Google limit. Google may use page text instead. A missing description leaves this task unfinished; it is not itself a ranking penalty.

Example

Illustrative copy: “Need boiler repair in Bristol? See the faults we repair, our service area and what to include when requesting an estimate.” Keep only claims the page supports.

  1. Summarize this page’s specific answer, service or resource.
  2. Use the main topic naturally without a keyword list.
  3. Save, open the published page source and search for name="description" to confirm the new text; use your editor’s published SEO preview if source is unavailable.
More help and optional notesMedium · Editor

Before you begin: SEO description edit access; otherwise use Blocked.

PassThe page has a specific, accurate description of its content and useful next step.
FailThe description is missing, misleading, obsolete or copied without page-specific value.

If it fails: Write an accurate page-specific summary.

Retest: Inspect the published description tag.

Not applicable: A non-HTML resource or a page deliberately outside this public-search review.

Optional: current description and corrected summary. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Choose a readable URL slug for a new page

A URL slug is the page-specific part of its web address.

Use this for: A new page, or an existing page with an independently justified move.

Open the URL or permalink setting. For a new page, choose a descriptive path using its main subject naturally and your site’s conventions. Do not rename a working established address merely to add a keyword or shorten it. A justified move needs an appropriate redirect and updated internal links; no universal slug length applies.

Example

For a new local service page, /boiler-repair-bristol/ is clearer than /service-item-8437/. Neither a fixed word count nor removing every small word is necessary.

  1. Choose a readable new path that describes the topic.
  2. Keep established URLs stable unless a real change justifies a move.
  3. For an approved move, test the old address and update internal links.
More help and optional notesHigh · Editor

Before you begin: Permalink access; a redirect plan for existing moves.

PassThe new address is readable and descriptive; any existing-page move has a justified, tested transition.
FailA new address is misleading or needlessly complex, or an established address is renamed without a transition plan.

If it fails: Use a descriptive path; plan justified moves.

Retest: Open the new and any changed old address.

Not applicable: An established page keeps its working address; cosmetic renaming is not required.

Optional: chosen path or approved reason and transition plan. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Use H1, H2 and H3 Headings to Explain the Page

Headings show the main topic and the sections that support it. Give the page a clear main heading, use H2s for major topics and H3s for details inside those topics. Include relevant search language where it accurately describes the section, then write an opening paragraph that answers or introduces that heading directly.

Write one clear main H1 heading

The H1 is the main visible heading readers see when they reach the page.

Use this for: A page you are preparing or improving.

Use your editor’s main heading setting to name the page’s subject clearly, including the primary phrase or a natural variation. Make it useful to someone who has just arrived. A clear main H1 is a practical convention; an exact H1 count is not a universal Google ranking requirement.

Example

Illustrative H1: “Boiler Repair in Bristol” is more informative than “Welcome” when the page actually offers that service in that area.

  1. Replace vague main headings with the actual topic.
  2. Set that heading to the page’s main heading level.
  3. Compare it with the title tag and opening answer.
More help and optional notesHigh · Website owner

Before you begin: Access to the page-heading editor.

PassThe main heading clearly identifies the topic and matches the page.
FailThere is no clear main heading, or it misrepresents the content.

If it fails: Write a descriptive main heading.

Retest: View the published heading outline.

Not applicable: The page is outside this public-search review.

Optional: a short note about the change. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Add descriptive H2 and H3 subheadings

Subheadings divide the page into useful topics rather than repeated keywords.

Use this for: Pages with a main topic and content sections.

Use the editor’s heading styles for H2 sections and H3 subsections. Put relevant supporting topics in headings where they describe the answer beneath them. Do not turn ordinary sentences into headings merely to repeat keywords, or choose a heading level only for its font size. Preview the resulting outline.

Example

Illustrative outline: H1 “Boiler Repair in Bristol”; H2 “Boiler Faults We Repair”; H3 “Leaks and Pressure Problems”; H2 “Requesting a Repair Estimate.” Include only genuine services.

  1. List the main sections the reader needs.
  2. Use H2 for those sections and H3 for supporting details.
  3. Write each heading to describe the content directly beneath it.
More help and optional notesMedium · Editor

Before you begin: The editor’s heading controls.

PassThe H2/H3 outline names useful sections in a logical hierarchy.
FailHeadings are vague, misleading, unnaturally repeated or assigned only for styling.

If it fails: Correct heading levels and vague labels.

Retest: Read the published heading outline.

Not applicable: A non-content utility view with no meaningful sections.

Optional: heading outline and confusing section. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Answer the main question near the beginning

The opening should give readers useful information before background or promotion.

Use this for: A page promising an answer, product detail or action.

Write the central answer near the opening, then put necessary conditions beside it. A service page should explain what is offered and where; a guide should give its usable answer or first step. Add a verified detail or clearly labeled original example. There is no required paragraph length or guaranteed AI extraction.

Example

Illustrative guide opening: “A boiler maintenance checklist covers the owner checks, service records and professional inspections needed for the specific system.” Explain the real scope; do not invent technical or safety advice.

  1. Write the main answer or service explanation first.
  2. Place essential conditions beside it.
  3. Follow with the details and examples readers need to act.
More help and optional notesHigh · Editor

Before you begin: Verified details supporting the answer.

PassThe opening supplies the promised answer or action with necessary conditions and useful detail.
FailThe answer is delayed, unclear or missing essential context.

If it fails: Lead with the answer and necessary conditions.

Retest: Find the answer on the published page.

Not applicable: Only for a utility page with no answer or visitor action.

Optional: missing or buried answer and proposed placement. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Use keywords naturally in the body copy

Relevant wording helps explain the topic when it adds meaning to the sentence.

Use this for: A page you are preparing or improving.

Use the main subject naturally in the opening and relevant supporting terms in the paragraphs that explain them. Read aloud and replace awkward repetition with ordinary wording. There is no ideal keyword density or mandatory exact-match count. Add a paragraph because it answers a real question, not to insert another variation.

Example

Instead of repeating “boiler repair Bristol” in every sentence, name the genuine fault, service area or booking step that sentence explains.

  1. Introduce the main subject clearly in the opening.
  2. Use supporting phrases in their relevant sections.
  3. Remove unnatural repetitions and unrelated terms.
More help and optional notesHigh · Website owner

Before you begin: The draft and its main topic.

PassThe wording describes relevant subjects naturally without forced repetition.
FailKeyword repetition or unrelated terms make the text less useful or readable.

If it fails: Rewrite awkward repetition around actual meaning.

Retest: Read the published copy aloud.

Not applicable: The page is outside this public-search review.

Optional: a short note about the change. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Add Useful Content and Truthful Trust Information

Useful on-page content answers the questions that affect a reader’s decision. Add real details, clear procedures and original examples where they improve the answer. Verify facts and identify the real person or organization responsible for the page when that information is relevant. More text or invented authority does not make a page more trustworthy.

Add useful details and verify important claims

Specific, supported information gives the page a reason to be useful.

Use this for: Pages containing factual claims or business details.

Check prices, coverage, dates, inclusions and factual claims against current reliable information. Replace generic promises with details this page can substantiate. Add a real example, limitation or useful explanation that competitors’ summaries do not supply. Do not invent experience, measurements or reviews; use qualified review when the subject requires it.

Example

A service page can explain its real coverage and estimate process. A checklist resource can show a completed fictional example. Neither needs an invented testimonial to add value.

  1. Add the missing detail that helps the reader decide or act.
  2. Verify factual claims and current conditions.
  3. Correct, qualify or remove unsupported wording.
More help and optional notesHigh · Editor

Before you begin: Current sources or a knowledgeable reviewer.

PassClaims match current evidence and attribution is truthful.
FailA claim, statistic, review or author credential is invented or unsupported.

If it fails: Correct, qualify or remove unsupported claims.

Retest: Verify the changed passage against its source.

Not applicable: No factual claims or change-sensitive details need verification.

Optional: claim, source, review date and required correction. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Show who is responsible for the content, where relevant

Readers should be able to identify the real source of important advice or business information.

Use this for: Pages where authorship, business identity or review context helps the reader.

Where authorship matters, add the real writer or reviewer and relevant, verifiable experience. For a business page, make its real identity and contact route easy to find. Use truthful publication or update dates. Never invent qualifications or a byline, and do not change a date without a meaningful content update.

Example

“Reviewed by an expert” is not acceptable unless the review happened. A truthful organization name and a clear source explanation are better than an invented credential.

  1. Identify the real author, business or responsible organization.
  2. Add accurate attribution and relevant contact or review information.
  3. Keep dates consistent with real publication and updates.
More help and optional notesHigh · Website owner

Before you begin: Verified author or business information.

PassDisplayed authorship, qualifications and dates are accurate and relevant.
FailThe page invents authority or displays misleading attribution or dates.

If it fails: Correct unsupported attribution.

Retest: Compare published attribution with the facts.

Not applicable: The page is outside this public-search review.

Optional: a short note about the change. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Prepare Image Files, Compression and Alt Text

Images should help explain the page without making it unnecessarily heavy. Prepare a suitable file before upload, give it a descriptive name and add an appropriate text alternative. Check the finished image on mobile as well as desktop. File format and compression choices depend on the image and the site’s requirements.

Name new image files descriptively

A descriptive filename gives useful context before an image is uploaded.

Use this for: New images or planned asset replacements.

Before uploading a new image, give the file a short descriptive name using the subject naturally. Keep its correct extension. A filename is a light contextual clue, not a reason to stuff keywords. Avoid renaming an established image URL solely for cosmetics; a change must preserve or update existing references.

Example

A new photo called “boiler-pressure-gauge.png” is clearer than “IMG_8437.png” if it actually shows a boiler pressure gauge.

  1. Choose a filename describing the visible subject.
  2. Upload the file through your normal media workflow.
  3. Check that the published page uses the intended image.
More help and optional notesHigh · Website owner

Before you begin: The new image file and upload access.

PassThe new file has an accurate descriptive name and works on the page.
FailThe filename is misleading or the replacement breaks the image.

If it fails: Rename before upload; correct broken references.

Retest: Reload the page and open the image.

Not applicable: The page has no relevant image.

Optional: a short note about the change. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Resize and compress images before upload

An appropriately prepared image stays clear at its displayed size without unnecessary weight.

Use this for: Pages containing informative, decorative or functional images.

Check the image’s displayed size, resize in an image editor, then export or compress it. Compare file size and clarity at the expected display size before uploading. Preserve readable labels. Use an efficient supported format when your workflow allows, while respecting required format policies. There is no universal kilobyte target.

Example

Illustrative sizing: a diagram displayed at 800 CSS pixels wide might use a 1,600-pixel source for a 2× display. Export that version, compress it, and compare file size and label legibility with the original. These dimensions are an example, not a universal target.

  1. Resize the source image for its intended display and needed detail.
  2. Compress or export it, then inspect the visual quality.
  3. Upload and check the image on desktop and mobile.
More help and optional notesMedium · Editor

Before you begin: An image editor and upload access.

PassThe published images load clearly with suitable dimensions and compression.
FailAn image is broken, unreadable or unnecessarily oversized for its use.

If it fails: Resize or compress without losing useful detail.

Retest: Inspect the uploaded crop, clarity and loading.

Not applicable: The page contains no images.

Optional: image dimensions, file size and the export that stays readable. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Write useful image alt text

Alt text explains an informative image when it cannot be seen.

Use this for: Informative, decorative or functional images on the page.

Open the image’s alternative-text field. Describe the meaning needed in this page’s context, using a relevant term only if natural. A linked image needs an accessible name explaining its destination or action. Pure decoration usually needs empty alt text. Do not repeat keywords, filenames or a nearby caption without useful purpose.

Example

For a relevant close-up, “Pressure gauge on the front of a boiler” is useful; a string of repair keywords is not. Adapt the wording to the real image.

  1. Identify whether the image informs, decorates or performs an action.
  2. Write the appropriate alternative in the image settings.
  3. Check the published image and its surrounding explanation.
More help and optional notesHigh · Website owner

Before you begin: The image’s purpose and alt-text field.

PassEach image has an appropriate alternative for its purpose.
FailA meaningful image lacks context or its alternative is misleading or keyword-stuffed.

If it fails: Describe its meaning or mark it decorative.

Retest: Review the page without images.

Not applicable: The page has no relevant image.

Optional: a short note about the change. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check Indexing, Mobile, Page Speed and Structured Data

Before publishing or finishing an update, check that the public page works and its technical settings match your intentions. An intended search page should be accessible and free of accidental indexing exclusions. Mobile usability, performance and truthful structured data support the page, but none guarantees a particular search result.

Check that an intended search page can be indexed

Public access and search inclusion are separate choices.

Use this for: A page you are preparing or improving.

Decide whether this page should appear in search. Inspect it with Search Console’s URL Inspection and check the editor’s indexing setting. Correct accidental noindex or access blocks only on pages intended for search. Private content needs access control. A passing live test does not guarantee indexing; later indexed information is separate.

Example

A launch page meant for search may accidentally retain a staging noindex instruction. A private account page should remain protected.

  1. Decide whether this page should appear in search.
  2. Inspect the current page and its relevant indexing settings.
  3. Correct only unintended exclusions, then retest.
More help and optional notesHigh · Website owner

Before you begin: The page and its indexing settings.

PassThe page’s access and indexing settings match its intended search status.
FailAn unintended restriction or response problem conflicts with that status.

If it fails: Correct the unintended restriction.

Retest: Repeat the live inspection.

Not applicable: The page is outside this public-search review.

Keep in mind: A passing live test does not guarantee indexing.

Optional: a short note about the change. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Make the page readable and usable on mobile

Mobile visitors need the same important answer and working actions.

Use this for: Pages intended for visitors on phones.

Open the published page on a phone or narrow screen. Read its main answer and inspect images, menus and the primary action. Fix clipped content, overlapping controls and difficult taps in the relevant layout setting. Keep important content available on mobile. Use a safe test environment or an approved test for submissions and purchases.

Example

A contact button that works on desktop but is covered by a mobile banner needs a layout fix. A guide’s diagram must remain readable without cutting off its labels.

  1. Read the answer and inspect the layout on a small screen.
  2. Follow links and use the relevant controls.
  3. Fix the specific layout or interaction problem and try again.
More help and optional notesHigh · Developer

Before you begin: A phone and safe interaction test.

PassText, media and controls remain usable and the main content is available.
FailOverlapping controls, hidden content or intrusive elements prevent the task.

If it fails: Repair the specific layout or control.

Retest: Repeat the affected mobile task.

Not applicable: Only for an explicitly non-mobile interface outside this review.

Optional: device/viewport, failed step and screenshot if appropriate. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Test page speed and address the main bottleneck

A performance test should lead to a specific improvement, not only a score.

Use this for: A page you are preparing or improving.

Run the page in PageSpeed Insights. Separate its real-user assessment from laboratory diagnostics, then investigate a relevant loading, interaction or layout problem. Fix the actual cause and rerun comparable tests. Missing real-user data is not a failure; a high laboratory score does not prove that every visitor has a good experience.

Example

If the main image is unnecessarily large, prepare a smaller readable asset and retest. Do not remove useful content merely to increase a score.

  1. Test the page and identify the type and scope of data shown.
  2. Choose a relevant diagnosed problem to investigate or fix.
  3. Retest with comparable settings and check the affected action.
More help and optional notesHigh · Website owner

Before you begin: The published page and performance test.

PassAvailable performance evidence is understood and no unresolved observed bottleneck prevents the intended task.
FailA reproduced loading, responsiveness or layout problem remains unresolved.

If it fails: Fix the diagnosed bottleneck.

Retest: Compare like-for-like tests and available field data.

Not applicable: The page is outside this public-search review.

Keep in mind: Use the technical checklist for detailed Core Web Vitals interpretation.

Optional: a short note about the change. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Add or correct relevant structured data

Structured data describes actual page content in a machine-readable form.

Use this for: Pages with an appropriate structured-data use case or existing markup to review.

Choose a structured-data type that genuinely fits the page. Enter accurate visible facts through your maintained site tool or developer implementation. Check vocabulary with Schema Markup Validator and supported Google features with the Rich Results Test. Correct errors and invented details. Valid markup does not guarantee a rich result; skip irrelevant types.

Example

A real product page can describe the actual product. An article about a business does not automatically justify a fictional LocalBusiness entity.

  1. Choose an applicable type for the real content.
  2. Enter accurate visible facts through the site’s supported implementation.
  3. Validate the published markup and correct mismatches.
More help and optional notesMedium · Developer

Before you begin: Structured-data edit access or developer help.

PassApplicable markup is truthful and meets the requirements of its chosen type.
FailMarkup invents entities, ratings, dates or details absent from the page.

If it fails: Correct unsupported facts and required fields.

Retest: Validate the published markup again.

Not applicable: No relevant structured-data implementation is useful for this page.

Optional: type, property mismatch and test result. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Review the published page after your changes

The published page is the result readers and search engines receive.

Use this for: A page whose approved changes have been published.

Publish the changes, then open the actual page rather than relying only on its editor preview. Check the title, description, main heading, revised copy, images and changed links. Confirm caching has not left an older version visible. Later search performance needs comparable observations; a completed edit does not guarantee more traffic.

Example

If the editor shows the new title but the public page still shows the old one, investigate publishing or caching rather than rewriting the title again.

  1. Open the live page and inspect the elements you changed.
  2. Follow links, open downloads and check the mobile view.
  3. Correct any publishing problem and review the final output.
More help and optional notesHigh · Editor

Before you begin: The public address and intended edits.

PassThe public page reflects the approved revision without new obvious defects.
FailOnly the editor preview was checked or the public page still shows stale content.

If it fails: Resolve the publishing or caching issue.

Retest: Inspect the changed page after publication.

Not applicable: No changes need publication; a pending required release is Blocked.

Keep in mind: A completed page review does not guarantee rankings or traffic.

Optional: uRL, changes, publication/retest date and outstanding issue. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Reset this checklist?

This removes saved statuses, evidence and result dates for the checks on this page. Other checklists keep their records. Export a CSV first if you need a copy.

Quick reference

On-Page SEO Checklist infographic

Keep these eight selected actions handy. The complete checklist above includes the steps, conditions and follow-up checks.

On-Page SEO Checklist infographic summarizing keywords, search intent, titles, descriptions, headings, internal links and image alt text. Text version below.
Eight selected actions from On-Page SEO Checklist. Use the complete checklist for steps, conditions and retests.
Read the infographic as text
  1. Choose one main keyword for the page
  2. Match the page to search intent
  3. Write an accurate, specific SEO title
  4. Write a page-specific meta description
  5. Use a clear, descriptive main H1 heading
  6. Answer the main question near the start
  7. Add relevant descriptive internal links
  8. Write useful alt text for informative images

Choose an action to open its full instructions above.

A useful result, every time

Check a task. Choose a result.

This is a manual SEO workflow. It helps you decide what to investigate and keep a usable record. It does not crawl your website or verify your answers automatically.

  1. Choose your scope. Pick the relevant task group and representative pages you are authorized to inspect.
  2. Run the stated check. Follow the steps, then choose your result. Click the square for Pass, or use the result menu for another status. You do not need to type anything.
  3. Assign the next action. Fix a problem when you can, or ask the right person for help. Optional notes can remind you what to do next. Check the result again after a fix.

What your progress means

Review progress counts passes and failures against applicable checks. Failed work still counts as reviewed. Blocked and untested checks remain unfinished. This is not an SEO score.

Untested
You have not checked this yet.
Pass
You checked it and it works as described.
Fail
You checked it and found something to fix.
Blocked
You need access, information or someone’s help.
Not applicable
This task does not apply to your website.

Export CSV downloads the checks currently shown and any optional notes. Print expands the instructions for that view. Saved results stay in this browser; there is no account sync.

A visual working guide

Connect the page to the visitor’s next step

An editorial sequence connecting a visitor task, an accurate page promise, a useful answer with evidence, and a relevant next step.
This is a practical content-planning framework, not a required heading pattern or a ranking formula. Original instructional illustration.
Apply the workflow

How Should You Apply This On-Page SEO Checklist to Your Page?

Use the same SEO elements for different page types, but adapt the keyword, examples and next action to what the page genuinely provides.

How Do You Use This as an On-Page SEO Audit Checklist?

For an existing page, start with its target query and current search intent, then work through the actual title, description, headings, content, images and links. Correct a specific issue when you find one. You do not need to type notes to use the checklist.

If a problem concerns server responses, robots rules or rendering, use the technical checklist. If it affects several templates or requires a broader traffic investigation, use the SEO audit checklist.

What Does a Useful On-Page SEO Edit Look Like?

Consider a hypothetical checklist page titled “Resources” whose opening contains only a company introduction. Rename the title and main heading to identify the real checklist, explain what it covers in the opening, and provide the working checklist or promised download.

The improvement is a clearer subject and a usable resource. Repeating the keyword more often would not repair a missing download or an unanswered question.

Which SEO Tasks Belong Beyond This Page?

This on-page SEO checklist focuses on one page’s topic, text and visible elements, with a few publishing checks. Use the technical checklist for detailed responses, redirects, crawl rules, canonicals, rendering and performance diagnostics. Use the audit checklist to investigate patterns across the website.

How Should You Optimize Different Page Types?

Optimize the elements around the task the page must complete. A service page needs a real offering, coverage and a useful next step. A product page needs accurate product details. An article needs a clear answer and supporting explanation. A checklist page needs actions someone can actually follow.

Use the main keyword to name that task naturally in the title and heading. Do not turn every page into a long article or add a sales pitch where the visitor needs instructions.

How Do Keywords Fit Into a Complete Page?

In a hypothetical local-service example, the main phrase is “boiler repair in Bristol.” The title and H1 identify that real service and place. H2s can describe genuine repair services, the actual service area and the estimate process. Each paragraph then explains the subject named in its heading.

For an informational resource, use the same relationship: a title that names the resource, a main heading that confirms it, and supporting sections that deliver the promised instructions. Use only facts you can verify and examples clearly identified as illustrative.

How Do You Turn Supporting Topics Into H2s and H3s?

Group related questions before writing headings. Put a broad subject at H2 level and a genuine subdivision at H3 level. Use the topic’s words naturally: “Service Area” and named real locations can help a service page, while “How to Use the Checklist” helps a resource page.

Avoid adding headings just to fit another keyword variation. Each heading needs a distinct useful explanation beneath it. Read the completed outline without the body to check whether the page’s structure makes sense.

Which Content Claims Should You Verify?

Verify details that could affect a reader’s decision: service availability, prices, qualifications, product behavior, dates, comparisons and claimed results. Match the strength of the wording to the evidence. A labeled hypothetical example explains an idea without pretending to be a customer case study.

Keep confidential supporting records private. Public citations, when allowed, should lead to the exact relevant source rather than an unrelated reputable homepage.

Which Images Make the Page More Useful?

Choose images that show a relevant detail, explain a sequence or compare something the reader needs to understand. A real product photo, an original diagram or a truthful screenshot can help. Decoration is acceptable, but it is not evidence that a product works or a result occurred.

Prepare the image for its display size, preserve useful detail during compression, and write appropriate alt text. Generated illustrations should not imitate real analytics results or unverified interfaces.

When Should You Update On-Page SEO?

Review the page when its facts, offering, audience questions or relevant search results change. Correct obsolete examples, broken links and information that no longer serves the task. Retest technical elements after a template or platform change.

Change an updated date when a real substantive revision occurred. Do not change only the year to imply a review that never happened. Earlier search performance is context for investigation, not a promise about the next result.

A clear process, with honest limits.

Follow the steps, choose the result that matches what you found, and check again after changes. Notes are optional. A completed check does not guarantee indexing, traffic or rankings. How the checklists work.