WordPress SEO Checklist for Beginners: Before You Publish

Good WordPress SEO begins with a page that answers a useful question and can be accessed by people and search engines. An SEO plugin can help manage settings, but its score is not a ranking promise.

Use this checklist for one page at a time. It covers the decisions you can check before publication and the signals worth reviewing afterwards. SEO means search engine optimisation: helping search engines understand a useful site and helping readers decide whether it meets their needs.

Step 1: Define the reader’s question

Write the main question the page should answer. Then identify what a reader needs to know to take the next practical step. A guide to building a portfolio should show examples and a process, not repeat the phrase “freelance portfolio” in every paragraph.

Look at your existing site before creating a new page. If another article already answers the same question well, improving it may serve readers better than publishing a near-duplicate. Give each page a clear purpose and link related guides together.

Step 2: Check that the public page is accessible

1. Confirm that the page is intended to be public and published, rather than a private draft.
2. Check WordPress’s search-engine visibility setting before launching a site. A staging site may intentionally discourage indexing; a public site usually should not.
3. Check any page-level noindex setting in your SEO tool.
4. Open the page while signed out and verify it is readable without an unexpected login.
5. Use HTTPS and fix broken destination pages or redirect loops.

Do not remove a privacy or access restriction from content that should remain private. Search visibility is a publishing decision, not something to enable indiscriminately.

Step 3: Write a clear title and organised headings

Use a title that names the subject and the value of the page. “How to Build a Freelance Portfolio When You Have No Clients” is specific. Avoid unsupported superlatives or adding a year solely to make an unchanged page seem current.

Use one clear page title and arrange sections with meaningful headings. Many themes render the title as an H1, so begin the article’s main sections with H2 headings. Use H3 for subsections. The structure should help readers scan and navigate.

Write a short SEO title if your tool allows it, while keeping it consistent with the actual page. Search engines may display a different title. There is no exact character count that guarantees the same appearance on every device.

Step 4: Make the article useful and checkable

Explain the process, show an example and name the limits of your advice. Check factual claims against appropriate current sources. Distinguish a hypothetical example from a real result, and do not invent first-hand experience or client outcomes.

Remove filler paragraphs that do not help answer the question. Include author information and update dates when they accurately reflect the page. A longer article is not automatically more useful than a shorter complete answer.

Google’s SEO Starter Guide is the primary reference for the broad principles here. Its advice supports clear, helpful pages rather than a mechanical keyword-density target.

Step 5: Check the URL, description and internal links

Before launch, choose a readable URL describing the subject. Once a page is established, avoid changing its address casually. A necessary change should include an appropriate redirect from the old address and updates to internal links.

Write a concise meta description that accurately summarises the page and gives a reader a reason to open it. It is a suggested summary, not a promise that Google will display that text or a direct way to buy a higher ranking.

Add links where readers need the next explanation. Use descriptive anchor text instead of repeating “click here”. For example, a proposal guide can naturally link to the guide to building a beginner portfolio. Check each destination rather than assuming the link works.

Step 6: Prepare images responsibly

• Use an image that adds context to the section.
• Resize and compress it for the display size rather than uploading an unnecessarily large original.
• Provide useful alternative text for informative images. Decorative images can use empty alt text.
• Keep important instructions available as text.
• Check image rights and avoid presenting illustrative images as evidence of real results.
• Keep dimensions or a stable image ratio to reduce layout movement.

Do not force keywords into every image description. Describe the relevant image’s purpose. An accessible description is more useful than a string of search phrases.

Step 7: Test the page on a phone

Read the opening, use the navigation and try the main links on a narrow screen. Look for tiny text, wide tables, overlapping elements and intrusive pop-ups. Check whether the featured image is correctly aligned and whether headings remain readable.

Test speed with a reputable tool, then investigate meaningful problems such as oversized images or unnecessary scripts. A performance score is diagnostic information, not a ranking guarantee. Check the actual page experience as well as the number.

Step 8: Review indexing and performance after launch

If you have Google Search Console, use URL Inspection for the published address. Confirm that the canonical URL and indexing information match your intent. Submitting a sitemap can help discovery, but it does not guarantee indexing or ranking.

Allow time for useful data. Review which queries lead to impressions and whether the page answers them. Improve a weak explanation or misleading title before assuming a new plugin will solve the problem. Record the date of substantial changes so later comparisons have context.

A seven-day improvement plan

1. Choose one important page and define its reader question.
2. Check public access and indexability.
3. Improve the title, introduction and headings.
4. Check facts, examples and missing explanations.
5. Fix links and prepare images.
6. Test mobile layout and investigate speed issues.
7. Publish improvements and record what changed.

Final publishing checklist

• The page answers one clear need.
• Its public access and indexing settings are intentional.
• The title and headings accurately describe it.
• Claims, examples and sources are checked.
• The URL, description and links are useful.
• Images are relevant, efficient and accessible.
• The page works on a phone.
• I have a plan to review performance.

Frequently asked questions

Do I need a perfect plugin score?

No. Use checks as prompts for review, not as instructions to damage a natural sentence or add unnecessary content.

How quickly will a page rank?

There is no fixed timetable. Discovery, indexing and ranking are separate, and none is guaranteed.

Should I add many similar keywords?

Use the language needed to explain the topic clearly. Repetition without useful information makes the page harder to read.

Your next step

Apply this checklist to one page and fix its largest practical weakness first. Keep a record of the change and review what readers actually do afterwards.