WordPress SEO Checklist for a New Website: A Practical Guide Using Yoast Free

You have launched your WordPress website, added your services and started publishing blog posts. Now comes a question many business owners face: what should you do next to help potential customers find it?

The temptation is to publish as much as possible. But before adding dozens of articles, check whether your existing pages are accessible, clearly organised and useful to the people you want to reach.

This WordPress SEO checklist provides a practical sequence for a new service-business website using Yoast SEO Free. It covers the technical setup, page content, internal links and measurement needed to build a useful foundation.

Installing an SEO plugin is one part of that work. Your content, offer and visitor experience need attention too.

Start with these priorities

If your website is new, use the following order to decide what needs attention first. These are recommended operational priorities, not a formula used by Google.

Priority	What to review	What a satisfactory result looks like
1. Access	Public availability and indexing settings	Important public pages are accessible and not unintentionally excluded
2. Services	Offer, audience and contact process	A visitor can understand what you do and how to enquire
3. Discovery	Navigation, internal links and sitemap	Important pages have clear routes for discovery
4. Content	Customer questions and article quality	Each page has a distinct purpose and useful information
5. Experience	Mobile layout, images and forms	The page is readable and its main actions work
6. Measurement	Search performance and enquiry quality	You can review what attracts relevant visitors and conversations

Work through the critical issues first. Rewriting a meta description can wait if the entire website is accidentally set to discourage indexing.

1. Check WordPress search engine visibility

In your WordPress dashboard, open Settings → Reading and find the search engine visibility setting.

For a public website you want search engines to index, the option labelled “Discourage search engines from indexing this site” should be unchecked. Save any intentional change.

The WordPress documentation explains that enabling this option asks search engines not to index the site. It does not make the website private or prevent normal visitors from accessing it.

Also check whether your live site is still behind a coming-soon screen or a login requirement. Open the homepage and a service page in a private browser window while logged out.

Recommended check: write down the exact URLs tested, the date and what a logged-out visitor can see. This gives you a clearer record than assuming that a page visible to an administrator is also visible publicly.

2. Distinguish crawling problems from indexing problems

A website can open in your browser while still having settings that affect search engines.

Google’s technical guidance distinguishes crawler blocking through robots.txt from indexing controls such as noindex. A robots.txt block is not a reliable method of removing a URL from search results.

For a page intended to appear in search, investigate unexpected crawler restrictions and noindex directives. A hosting firewall or security configuration can also require technical review.

Do not replace your robots.txt file with a generic template without understanding the existing rules. If a developer manages the website, give them the affected URL and the exact message from Search Console rather than asking them to “fix all SEO.”

That makes the work specific and reduces the chance of changing unrelated settings.

3. Set up Search Console and inspect important pages

Verify your website in Google Search Console using an available method appropriate to your access. Then inspect the homepage, a main service page and a recent blog post.

Google’s SEO Starter Guide identifies URL Inspection as a way to understand how Google sees a page.

For your own review, maintain a short tracking sheet:

URL	Intended purpose	Reported issue	Next action	Review date
Homepage	Introduce the business	Record the actual finding	Assign a specific task	Choose a date
Service page	Explain the offer	Record the actual finding	Assign a specific task	Choose a date
Blog article	Answer a customer question	Record the actual finding	Assign a specific task	Choose a date

Interpret the findings page by page. A deliberately excluded utility page is a different situation from an excluded service page.

When troubleshooting, change one clearly identified cause and review the result. Avoid repeatedly changing titles, URLs and technical settings at the same time; that makes the investigation harder to follow.

4. Review Yoast SEO Free without chasing every green light

Yoast SEO Free provides content analysis based on your chosen focus keyphrase. Its SEO analysis documentation describes checks across elements such as the title, URL and meta description.

For a new article, my recommended workflow is:

1. Identify the reader’s main question.
2. Choose a focus keyphrase that describes it accurately.
3. Write a useful first draft.
4. Enter the SEO title and meta description.
5. Review the plugin’s suggestions.
6. Make changes that improve the page without forcing unnatural wording.

A focus keyphrase is an input for the plugin’s analysis, not a request that reserves a ranking for your page. A green indicator is not evidence that the article satisfies every customer need.

For example, a page could mention “WordPress SEO checklist” in several places while giving no usable instructions. Another could explain a problem well using natural variations. Editorial judgement remains essential.

5. Enable and submit your XML sitemap

According to Yoast’s sitemap instructions, you can find the setting under Yoast SEO → Settings → Site features. Under Technical SEO, enable XML sitemaps if appropriate and use the option to view the sitemap.

Yoast’s typical sitemap index address ends in:

/sitemap_index.xml

Confirm the actual address on your website rather than assuming it works. Yoast updates its sitemap as content changes; content types marked as noindex are excluded.

Then follow Yoast’s submission guidance to add the sitemap index in Search Console’s Sitemaps section. A domain property may require the complete sitemap URL.

Google describes sitemaps as useful for discovering URLs, including on recently launched websites, in its recrawling guidance. Submission does not guarantee indexing or a particular ranking.

Recommended check: inspect whether your main public pages are represented. If an important page is missing, investigate its settings before manually adding extra sitemap tools.

6. Choose clear URLs and preserve them

For a new article, choose a short, understandable slug that describes its subject.

For example:

• Clear: /wordpress-seo-checklist/
• Less useful to a reader: /new-post-final-seo-guide-123/

An evergreen URL is convenient when you expect to update the article over time. You can revise the content without renaming the address each year.

For a page that is already live, weigh the benefit of a URL change against the maintenance it creates. If a change is necessary, plan the appropriate redirect and update internal links. Do not change an established URL only to gain a small improvement in a plugin score.

In my recommended editorial record, every article has a title, URL, primary question and related service. That record helps prevent accidental duplication as publishing frequency increases.

7. Give every important page a clear purpose

Before writing, complete this sentence:

“This page helps this type of visitor make this decision or complete this task.”

A website design service page might help a business owner decide whether to enquire about a project. A redesign checklist might help that person prepare requirements. They are related, but they serve different needs.

Use the distinction to decide what belongs on each page.

Page	Recommended content
Service page	Scope, suitability, process, supporting evidence and enquiry route
Tutorial	Prerequisites, steps, checks and common problems
Comparison	Decision criteria, trade-offs and suitable use cases
Case study	Starting situation, work performed, documented outcome and limitations

Avoid creating several articles that repeat the same advice with slightly different titles. If two drafts answer the same question for the same audience, consider combining them into a more useful resource.

8. Write titles and descriptions that set accurate expectations

I recommend writing a title that identifies the topic and the value of the page. Avoid packing your entire service list into every article title.

For example:

WordPress SEO Checklist for a New Website

is easier to evaluate than:

Best SEO WordPress Marketing Website Ranking Services Guide

Write a unique meta description summarising what the reader will find. Google’s snippet guidance explains that snippets are usually generated from page content, though the meta description may be used. Your supplied description is not guaranteed to appear exactly as written.

For a service-business blog, the description should help a suitable visitor recognise that the article addresses their problem. Avoid promises of instant ranking improvements or guaranteed results.

9. Structure articles for reading and action

Use a clear main title, followed by sections that follow a sensible sequence. For tutorials, that normally means prerequisites first, implementation next and verification afterward.

My preferred review questions are:

• Can someone understand the page’s purpose from the introduction?
• Do headings explain what each section covers?
• Does every instruction say what to check afterward?
• Are examples labelled clearly?
• Can someone find the next step without scrolling through a long sales pitch?

Keep paragraphs focused. Use tables when readers need to compare options and numbered lists when order matters. A table of contents can help with a substantial guide, provided its links work and it does not dominate the mobile screen.

Do not add sections merely to make the article longer. Google’s people-first content guidance prioritises useful, original information and explicitly rejects the idea of a preferred word count.

10. Improve images without making the page heavy

Use images when they help explain the content. An annotated screenshot may be more useful in a setup tutorial than several decorative graphics.

Google’s image guidance recommends attention to image quality, responsive delivery and loading performance. It also explains that meaningful image content should be discoverable through supported HTML image elements.

For your publishing workflow, I recommend:

• Resize images to suit their intended display.
• Compress files while preserving readable text and useful detail.
• Describe meaningful images accurately in alt text.
• Avoid inserting keywords that do not describe the image.
• Check that screenshots remain understandable on a phone.

A purely decorative image should not receive a forced keyword description. For a screenshot, make sure the instruction is also explained in the surrounding text so the reader does not depend entirely on the image.

11. Test the mobile experience and loading behaviour

Open your homepage, a service page and a long article on a phone. Test the navigation, tables, buttons, forms and any sticky contact elements.

Look for practical problems: text extending beyond the screen, a large banner pushing the introduction far down, or a floating button covering the submit control.

For performance, the Core Web Vitals guidance identifies good thresholds of LCP at 2.5 seconds or less, INP at 200 milliseconds or less, and CLS at 0.1 or less, evaluated at the 75th percentile of visits.

Use those metrics as diagnostic information. A new site may not yet have sufficient real-user data, and a laboratory performance test is not the same as an assessment of all visitors’ experiences.

My recommendation is to prioritise observable problems and retest after each meaningful change. Avoid installing multiple optimisation plugins with overlapping responsibilities simply to chase a score.

12. Build links between related articles and services

Google’s Starter Guide explains that links help it discover pages. They also give readers useful routes through a website.

For each new article, choose a relevant next destination. It might be a related tutorial, a comparison or a service page.

For instance, readers who want to understand how these fundamentals relate to newer search terminology can continue to SEO vs GEO vs AEO: What Actually Matters for Google Search in 2026?.

I recommend revisiting older relevant articles when you publish something new. Add a link only where it helps the existing explanation.

Use descriptive link wording and avoid repeating an exact keyword phrase across every page mechanically. The reader should understand what they will find at the destination.

13. Review canonical settings carefully

Yoast adds canonical URLs and provides an advanced field for overriding them when needed. For a normal original article, you generally do not need to enter a custom canonical manually.

A canonical identifies a preferred URL; it is not a way to describe which service a blog promotes. Do not point every article’s canonical to the homepage or a service page.

If there is a duplicate-content or migration issue, investigate the specific URLs before changing the setting. Preserve a record of the reason for any override so a future editor can understand it.

14. Make the author, business and offer easy to evaluate

A new website has little history for visitors to inspect. Help them understand who is behind it.

My recommended baseline includes an accurate author introduction, clear service descriptions and working contact details. Where appropriate, add genuine work examples with permission.

Avoid fabricated testimonials or unsupported claims about client results. If you demonstrate a process on a sample website, label it as a demonstration.

For a service page, explain the information needed to start a conversation. For example: the website URL, main challenge and desired outcome. This can produce a more useful initial enquiry than a generic “Contact us for everything” message.

15. Test and measure enquiries

Traffic is only part of the picture for a service business. You also need to know whether visitors can contact you and whether those conversations are relevant.

Submit a test enquiry from a phone. Confirm receipt, check the success message and review the follow-up process. Repeat this after significant form, caching or security changes.

My suggested measurement categories are:

Measure	What it tells you	What it does not prove
Search impressions	Your pages appeared for reported searches	That every appearance reached the right customer
Search clicks	Someone selected your result	That the visitor became a lead
Contact-link clicks	Someone expressed possible contact intent	That a conversation happened
Successful form submissions	An enquiry was sent	That the enquiry is suitable
Qualified enquiries	The prospect fits your service criteria	That a sale has been completed

Choose suitable analytics tools and implement them with attention to consent and the data collected. Avoid sending names, email addresses or message contents into general analytics events.

Review enquiry quality with the person who responds to customers. That feedback can shape the next article more usefully than page-view totals alone.

How often should a new website publish blogs?

For a small service website, I recommend starting with two substantial articles per week for the first eight to twelve weeks, provided each has a distinct purpose and receives proper review. This is a proposed workload, not a Google requirement.

If that pace reduces quality, publish less frequently. Reserve time for service-page improvements, distribution and updates to existing articles.

Google’s people-first guidance cautions against adding content mainly to make a website appear fresh. A useful publishing programme is built around the information your audience needs.

Here is an example weekly routine:

Day	Suggested task
Monday	Publish a practical tutorial
Tuesday	Share it with an audience likely to benefit and review relevant internal links
Wednesday	Improve a service page or older article
Thursday	Publish a comparison or customer-problem article
Friday	Check implementation, enquiries and lessons for future briefs

The goal is a growing collection of helpful resources with clear connections, not a growing count of near-identical posts.

A three-month plan for a new service-business blog

Month one: build a useful foundation

Complete the critical technical checks. Clarify your main services and publish answers to questions prospective customers ask before enquiring.

For a digital marketing website, that could include this WordPress SEO checklist, an SEO audit guide and a discussion of why website traffic does not always produce enquiries.

Month two: address decisions and objections

Use real questions from conversations to guide comparisons and deeper tutorials. Explain what affects project scope, how to evaluate a proposal and what clients need to prepare.

Review whether existing articles connect naturally to the appropriate service pages. Improve those connections where readers would benefit.

Month three: refine the programme using evidence

Review search queries, visits and enquiry quality together. Expand subjects that attract suitable readers, and improve pages that fail to answer the intended question.

Where traffic remains low, treat conclusions as provisional. Three months is a review point for the work, not a guaranteed deadline for rankings or revenue.

A final checklist before each article goes live

• The article answers a distinct customer question.
• Factual claims and links have been checked.
• The title, slug and description accurately describe the content.
• The headings follow a logical order.
• Images are useful, appropriately sized and described.
• Relevant internal links lead to working pages.
• The intended indexing settings are correct.
• Mobile layout and tables have been previewed.
• The next step is appropriate to the reader’s needs.
• The article is recorded in the editorial plan for future review.

Frequently asked questions

Is Yoast SEO Free enough for a new WordPress website?

It supports important foundational tasks, including content analysis and XML sitemaps. Start by implementing those tasks well. Additional tools should address an identified requirement; paying for a plugin does not replace useful content or a working website.

Should I publish a blog every day?

Only if you can consistently provide distinct, well-reviewed content and maintain the rest of the website. For a small team, I recommend a manageable schedule with time for revisions and promotion.

Will submitting a sitemap make Google index every post?

No. It helps with URL discovery but does not guarantee indexing. Investigate individual pages through Search Console when an important URL is not appearing as expected.

Should every page use the same focus keyphrase?

I recommend mapping each important page to a distinct primary need. Related vocabulary will naturally overlap, but copying one focus phrase across unrelated pages makes planning less useful.

Do I need a very long article to compete?

Use enough detail to resolve the reader’s problem. A thorough tutorial may need substantial space; a narrow question may not. Remove repetition even when it reduces the word count.

Should I change an existing URL to add a keyword?

Do not make that change automatically. Consider existing links, traffic and the purpose of the page. If a URL change is justified, plan the redirect and update affected links.

Turn the checklist into a working plan

Begin with three URLs: your homepage, a key service page and one article. Review access, purpose, internal links, mobile usability and the contact route for each.

Record the problems, assign the next actions and verify the fixes. Then apply what you learn to the next group of pages.

Need help setting up or improving your WordPress website’s SEO? Share your website URL, the main issue and your business goal with Suraj Anjaana to discuss suitable next steps.

• Email: ceo@surajanjaana.com
• WhatsApp: +91 8860487805
• Website: surajanjaana.com

About the author: Suraj Anjaana works across SEO, link building, social media optimization, PPC, website design and development, sharing practical digital marketing guidance for businesses.

Relevant link : audit your website’s enquiry journey