Yoast SEO installed is not Yoast SEO configured. Most WordPress sites have the plugin active, the traffic lights scattered across their post editor, and zero confidence that the underlying settings are actually doing anything useful. The plugin ships with defaults — and defaults are not a strategy.
This is not a guide about chasing green dots. This is about every configuration layer that Yoast buries under tabs that look optional — schema, sitemaps, social meta, breadcrumbs, RSS behavior, robots directives — and what happens when you leave them at factory settings.
Let's go through every major setting with intent.
Start With the Configuration Wizard — Then Override It
Yoast prompts you with a Setup Wizard on first install. Run it. But treat the output as a first draft, not a finished configuration. The wizard establishes your site type and basic identity — that data feeds directly into your schema markup, which affects how Google interprets your structured data at the page level.
After the wizard, go to SEO → General → Your Info. Confirm your site name, separator character, and whether your site represents an Organization or a Person. This is not cosmetic. Yoast uses this data to build Organization or Person schema on every page. If you're a business, choose Organization and upload your logo. If it's a personal brand, choose Person. A mismatch here means your Knowledge Graph data is wrong from day one — and Google uses that data to construct your entity profile in search.
Set your site separator while you're here. The | and – characters render differently depending on the device and font stack. Pick one and commit — it's part of your title template, and title templates propagate to every post, page, and custom post type on the site.
Search Appearance: The Section Most People Abandon Halfway
Go to SEO → Search Appearance. This controls what gets indexed, what gets a title template, and what gets excluded from search entirely. Most people open it, change the homepage title, and leave.
Content Types tab: Every post type — posts, pages, custom post types — gets its own title and meta description template. The default %%title%% %%sep%% %%sitename%% works for most situations. But for WooCommerce product pages, you may want to surface category or price context in the template. For archive pages that produce thin content, set them to noindex. That decision has to be deliberate — Yoast won't make it for you.
Taxonomies tab: Categories and tags get indexed by default. For content-heavy category archives with dozens of posts, that's fine. For small sites where a tag archive contains two posts and no original content, that's a duplicate content risk. In most site audits we perform, tag archives are left indexed by default, generating hundreds of thin pages that split crawl budget and dilute topical authority. If your taxonomy archives don't earn independent search value, set them to noindex.
Media tab: This one matters more than it looks. By default, WordPress creates a unique URL for every uploaded image — a near-empty page with no search value. Yoast includes a one-click toggle to redirect those attachment URLs to the parent post or the media file itself. Enable it. In most audits we perform, this setting is still off, meaning every historical image upload has been generating an indexable stub page. Fixing it retroactively improves crawl efficiency over time.
Sitemaps: What to Include, What to Cut
Go to SEO → General → Features and confirm XML Sitemaps is enabled. Your sitemap lives at yourdomain.com/sitemap_index.xml. Submit it in Google Search Console. That part most people do.
What most skip: excluding post types and taxonomies that don't belong in the sitemap.
If you have a custom post type for internal use — staff records, form submissions, private documentation — those URLs shouldn't be in your sitemap. In Search Appearance → Content Types, toggling off Show in search results for a post type removes it from the sitemap automatically.
For high-volume WooCommerce stores, sitemap size becomes its own problem. Product variations can generate thousands of URLs, many of which share near-identical content. Use WP-CLI to get a fast count of published products:
wp post list --post_type=product --post_status=publish --format=count
If that number is far higher than your distinct, canonical product count, you have an indexation problem that Yoast's sitemap exclusions only partially address. But sitemap configuration is the first lever to pull.
Also: after any significant Yoast reconfiguration, flush transients. Yoast uses its own transient layer to cache sitemap data, which means changes may not reflect immediately in production. Flush via WP-CLI:
wp transient delete --all
Then resubmit the sitemap in Search Console. Skip this step and you'll spend 20 minutes wondering why your sitemap still shows excluded URLs.
Schema: The Setting That Actually Moves the Needle
Go to SEO → Search Appearance → Content Types, then click any post type. Open the Schema tab. This is where you set the default Article type and Page type per content type.
For standard blog posts: Article → Article or BlogPosting.
For news content: NewsArticle.
For WooCommerce products: Yoast + WooCommerce handles Product schema automatically.
For custom post types: the default is often None — meaning no structured data output for those URLs.
Schema is what drives rich results: FAQ dropdowns, article dates, breadcrumb paths in SERPs. Leaving it on None for key content types is leaving structured data signals completely unconfigured. Go through every active post type and make a deliberate call.
If your staging workflow involves cloning the live site, check that the schema settings carry over. Yoast stores most of its configuration in wp_options — a staging clone will have the correct settings, but changes made on staging won't automatically sync to live. Establish a process: document your Yoast settings, and push changes from staging to live deliberately rather than assuming parity.
Social Meta: Open Graph and Twitter Cards Done Right
Go to SEO → Social. Enable Open Graph metadata and Twitter card metadata. Both should be on.
Then do three things most installs skip:
1. Set a default social image. Each social tab has a fallback image field. Without it, social shares on pages without a featured image pull a random element from the page — or render blank. Set a clean, branded fallback at the correct dimensions (1200×630px for Open Graph).
2. Add your Facebook App ID and Twitter username. The App ID enables Facebook Insights for your domain. The Twitter handle ensures the twitter:site tag populates correctly, which affects how Twitter Cards render when your URLs are shared.
3. Check social preview per post. In the Yoast block in the post editor, the Social tab shows exactly how that URL renders on Facebook and Twitter. Most content teams never open this tab. The og:title tag often pulls the raw SEO title rather than a tailored social headline — and long SEO titles get truncated badly in social previews.
On sites running multiple SEO-adjacent plugins — Rank Math remnants, a page builder with its own Open Graph output, All in One SEO left partially active — duplicate meta tags accumulate. Do a view-source check after configuration:
Ctrl+U → search for "og:title"
If it appears more than once, you have a conflict. Yoast should be the sole source of SEO meta on any URL. Disable meta output on every other plugin touching the document head.
Breadcrumbs, RSS, and the Robots Directives People Ignore
Breadcrumbs: Go to SEO → Search Appearance → Breadcrumbs. Enable them. Then implement them via your theme using Yoast's function or block. Yoast-generated breadcrumbs produce BreadcrumbList schema, which renders as structured URL paths in SERPs. A theme's native breadcrumb component won't produce this schema. Most don't.
<?php
if ( function_exists('yoast_breadcrumb') ) {
yoast_breadcrumb( '<p id="breadcrumbs">','</p>' );
}
?>
RSS: Under SEO → General → RSS, Yoast lets you prepend or append content to your RSS feed. Add an attribution link back to your domain. When scrapers republish your feed — and they do — they republish that attribution with it. Minor deterrent, low-effort setup.
Robots directives: In the Yoast Advanced tab on individual posts and pages, you can set per-URL robots directives: noindex, nofollow, noarchive. Use this for thank-you pages, login redirects, and any page that shouldn't be indexed but can't be restricted at the server level. A properly configured .htaccess file handles access control — Yoast handles indexation signals. Both layers matter and they serve different purposes.
The Conflict No One Checks For
Yoast removes several default WordPress head outputs: the shortlink, the generator meta tag (which exposes your WordPress version — a meaningful security signal), and redundant meta outputs from other plugins. That's useful default behavior.
But on sites where the object cache is running — Redis, Memcached, or a host-level page cache — Yoast's meta tags sometimes fail to update after configuration changes. The cache serves stale head data. Use Query Monitor to inspect what's actually rendering in the document head versus what Yoast reports in the admin. The discrepancy is usually a cache flush issue, not a Yoast misconfiguration — but the SEO outcome is identical: wrong meta tags in production, invisible to you in the dashboard.
This is also where PHP version compatibility matters more than most site owners realize. Running PHP 7.4 on a site where Yoast has shipped updates optimized for PHP 8.x can produce subtle output inconsistencies — not fatal errors, just quiet functional gaps in structured data rendering. Check your PHP version and keep it current. It's one of those maintenance items that doesn't break anything visibly until it does.
What Correct Configuration Actually Accomplishes
Proper Yoast setup is not about green dots. It's about signal hygiene.
Google needs clean, consistent signals: what type of content this is, what it's about, what the canonical source is, how it fits your site architecture. Misconfigured schema tells conflicting stories. Unexcluded attachment pages dilute crawl budget. Missing Open Graph defaults break social distribution. Indexed tag archives with two posts each split topical authority across thin pages that serve no one.
None of this is dramatic. None of it crashes your site. It quietly undermines the SEO work you're doing everywhere else — content production, link building, page speed optimization — because the foundational signals are noisy.
Across dozens of WordPress site audits, the same Yoast misconfigurations appear without fail: media attachment pages still indexed, tag archives left on, social fallback images absent, schema type set to None on key content types. These aren't beginner mistakes — they're default mistakes. The plugin feels active. It's not configured.
If You'd Rather Not Do This Alone
Correct Yoast configuration is one checkpoint in a broader WordPress SEO and maintenance picture. Sitemaps need updating as content grows. Schema needs review when site structure changes. Social meta needs testing when new post types are added. It's not a one-time task.
Our WordPress care plans include SEO configuration audits as part of ongoing site management — not a one-time fix, but a standing protocol applied whenever the site changes in a way that affects search signals.
If you'd like to start with a focused review of what's currently misconfigured, see what we cover in a full WordPress audit. You'll know exactly what state your Yoast setup is in before we touch anything.
Ongoing management plans start from transparent, flat-rate pricing — no opaque retainers. Review pricing here.
Look — I'm writing this because this is a problem I see constantly, and it's also exactly what we built Vimsy to solve. If you want professionals handling this instead of hoping nothing breaks, book a free call.
A correctly configured Yoast install doesn't announce itself. It just quietly does what you set it up to do — and stops quietly working against you.
