If you run a WordPress site, sooner or later somebody tells you to install Yoast SEO. It is one of the most widely used plugins in the WordPress ecosystem, and for a lot of site owners it is the first piece of SEO tooling they ever touch. That popularity cuts both ways. The plugin genuinely removes a pile of fiddly technical work, and it also encourages a habit — chasing coloured bullets — that has very little to do with how search engines actually rank pages.
This is an independent review. We have no relationship with the plugin's developers, and nothing below is a recommendation to buy anything. The aim is simply to describe what the plugin handles for you, what it leaves on your plate, and how to set it up without turning your site into a settings project.
What the Plugin Actually Is
Yoast SEO is a WordPress plugin, maintained by an independent software company, that adds an on-page optimisation layer to the editor and a set of site-wide technical defaults to the admin area. Strip away the marketing and it does three distinct jobs:
- It controls your metadata. Title tags, meta descriptions, canonical tags and robots directives become editable fields per post, per page and per content type, instead of whatever your theme happened to output.
- It generates technical files. An XML sitemap is produced and kept current automatically, and social markup such as Open Graph and Twitter card tags is added to your pages.
- It scores your draft. As you write, it runs a content analysis against a focus keyphrase and a separate readability analysis, and reports both as a list of pass/fail checks.
The first two are the valuable part. They are plumbing — dull, repetitive, easy to get wrong by hand, and exactly the sort of thing a plugin should own. The third is the part everybody talks about and the part that needs the most caution.
How the Analysis Works
You give the plugin a focus keyphrase. It then checks your draft for a list of conditions: does the phrase appear in the title, in the first paragraph, in a subheading, in the slug, in image alt text; is the text long enough; are there internal and outbound links; is the meta description present and a sensible length. Alongside that, the readability pass looks at sentence length, paragraph length, passive voice, transition words and how often consecutive sentences start with the same word.
The snippet preview is the single most useful widget in the box. It renders an approximation of how your title and description might appear in results, which makes it obvious when a title is going to be truncated. Worth knowing, though: Google generates the displayed text itself and frequently rewrites both the title link and the description based on the query. Google's own documentation on how snippets are created is explicit about this. Treat the preview as a drafting aid, not a promise.
Where the analysis misleads people is that it measures the presence of things, not the quality of them. It cannot tell whether your article answers the question a searcher had. It will happily award a green light to a page that repeats a phrase in all the right slots and says nothing anyone needed. Google's guidance on creating helpful, people-first content is the corrective here: write for the reader, then use the checklist to catch the mechanical omissions.
Setting It Up Without Over-Configuring
Installation is the standard WordPress route — add the plugin from the directory, activate it, and the configuration workflow starts on first load. That workflow asks a short series of questions about the type of site you run, whether it represents an organisation or a person, and which content types should appear in search results. Answer them honestly and you can leave nearly everything else alone.
The settings that actually matter
- Content type visibility. Decide which archives and taxonomies should be indexable. Most small sites should exclude tag archives, author archives on a single-author blog, and attachment pages. This is the single biggest win in the whole settings screen, because it stops thin duplicate pages competing with your real ones.
- Title and description templates. Set sensible patterns per content type once, then override individually only where it matters. This is far more maintainable than writing every title by hand.
- The XML sitemap. It is on by default and it updates itself. Confirm the URL loads, then submit it once. Google's guide to building and submitting a sitemap covers what belongs in it.
- Social markup. Set a default sharing image so links to pages without a featured image do not appear bare when they are shared.
- Webmaster verification. The plugin will hold verification tokens for the major search consoles, which saves you editing theme files.
Beyond that sits a second tier of tools — bulk editors for titles and descriptions, a file editor for robots.txt, import and export utilities, and redirect handling in the paid tier. Useful when you need them, and entirely ignorable until then. If you are building a site from scratch, our guide to building an SEO-friendly WordPress site covers the structural decisions that come before any of this.
Free Versus Paid
The free version covers the whole technical layer: metadata control, sitemaps, social markup, indexation settings and the single-keyphrase analysis. That is genuinely everything a small site needs. The paid tier adds convenience and scale features — analysis against multiple related phrases and synonyms, internal linking suggestions, per-network social previews, and a redirect manager that offers to create a redirect when you change or delete a URL.
Pricing is a per-site annual subscription and is tiered, so treat any figure you read elsewhere as out of date and check the source. The honest way to think about the upgrade is this: buy it for the redirect manager and the linking suggestions if you publish often and change URLs often. Do not buy it expecting the multi-keyphrase analysis to move rankings. It will not.
What It Cannot Do
This is the section most reviews skip, so here it is plainly.
- It does not rank your site. Nothing in the plugin creates authority. Green lights across the board on a page nobody links to and nobody wants to read produce exactly nothing.
- It does not write or edit for you. The readability score is a crude proxy for prose quality and is easily gamed by chopping sentences in half.
- It does not fix site speed. Page experience work — layout stability, load performance, image weight — sits entirely outside its scope. That is a theme, hosting and asset problem.
- It does not fix your information architecture. If your categories overlap and your navigation is a maze, no plugin repairs that.
- It cannot make a poor keyword choice work. Targeting is a research decision made before you open the editor; see our roundup of keyword research tools for the step that comes first.
The Verdict
Install it, spend twenty minutes on indexation settings and title templates, then largely forget it exists. Used that way, it is a solid piece of infrastructure that quietly prevents a category of technical mistakes. Used as a scoreboard, it turns writing into a box-ticking exercise and makes your prose worse.
The plugin is one of several credible options in this space — we compare the field in our list of SEO plugins for WordPress, and more of our search coverage sits in the SEO section. Whichever you choose, pair it with Google's SEO starter guide and a habit of publishing things worth reading. That combination beats any plugin configuration.