<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Riichi Mirza</title>
    <description>The latest articles on DEV Community by Riichi Mirza (@riichimirza).</description>
    <link>https://dev.to/riichimirza</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4205717%2F24dca5c3-01f7-45d3-9e37-7e48c0527ad9.png</url>
      <title>DEV Community: Riichi Mirza</title>
      <link>https://dev.to/riichimirza</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/riichimirza"/>
    <language>en</language>
    <item>
      <title>Pagination, Author Archives and Date Archives on Small WordPress Sites: What to Index in 2026</title>
      <dc:creator>Riichi Mirza</dc:creator>
      <pubDate>Mon, 26 Oct 2026 23:21:00 +0000</pubDate>
      <link>https://dev.to/riichimirza/pagination-author-archives-and-date-archives-on-small-wordpress-sites-what-to-index-in-2026-3p5d</link>
      <guid>https://dev.to/riichimirza/pagination-author-archives-and-date-archives-on-small-wordpress-sites-what-to-index-in-2026-3p5d</guid>
      <description>&lt;p&gt;Small WordPress sites rarely have a "crawl budget" crisis, but they almost always have crawl &lt;em&gt;waste&lt;/em&gt;: hundreds of URLs like &lt;code&gt;/page/7/&lt;/code&gt;, &lt;code&gt;/author/admin/&lt;/code&gt;, &lt;code&gt;/2023/04/&lt;/code&gt; and &lt;code&gt;?page=3&lt;/code&gt; that duplicate content you already have. None of these will get you penalized. They just dilute where Google spends attention and where your internal links point. Here is a practical, 2026-aware way to handle them.&lt;/p&gt;

&lt;h2&gt;
  
  
  First, the rel=next myth
&lt;/h2&gt;

&lt;p&gt;Google confirmed back in 2019 that it no longer uses &lt;code&gt;rel="next"&lt;/code&gt; and &lt;code&gt;rel="prev"&lt;/code&gt; as an indexing signal. In 2026 that is still true. Adding them will not help rankings, and removing them will not hurt. (Bing and some accessibility tools may still read them, so leaving them in place is harmless.)&lt;/p&gt;

&lt;p&gt;What &lt;em&gt;does&lt;/em&gt; matter is simpler:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Each paginated page should be crawlable via normal &lt;code&gt;&amp;lt;a href&amp;gt;&lt;/code&gt; links, not only via JavaScript "Load more" buttons.&lt;/li&gt;
&lt;li&gt;Each page should be self-canonical (page 2 canonicals to page 2, not to page 1).&lt;/li&gt;
&lt;li&gt;Paginated pages should not be the main way Google finds your important posts.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Pagination: /page/2/ and beyond
&lt;/h2&gt;

&lt;p&gt;WordPress creates &lt;code&gt;/blog/page/2/&lt;/code&gt;, &lt;code&gt;/category/x/page/3/&lt;/code&gt; and so on automatically. The common mistakes:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Canonicalizing page 2+ to page 1.&lt;/strong&gt; This tells Google the deeper pages are duplicates, so posts linked only from them can become harder to discover. Keep pagination self-canonical. If canonicals are new to you, read &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;how to fix duplicate content with canonical tags&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Noindexing page 2+ and assuming it is fine.&lt;/strong&gt; Long-term noindex can lead Google to crawl those pages less and eventually treat their links as less important. It is usually acceptable on tiny sites, but it is better to make sure every post is also reachable via categories, internal links and your sitemap.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pagination 40 pages deep.&lt;/strong&gt; If your oldest post sits on &lt;code&gt;/page/38/&lt;/code&gt;, it is seven clicks from home. Raise posts per page (12–20 is fine), and link evergreen posts from hub pages.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  View All vs paginated lists
&lt;/h2&gt;

&lt;p&gt;A "View All" page used to be recommended as the canonical target. Today the guidance is: use it only if it loads fast. For a site with 60 posts, a single archive with titles and excerpts can work well, and you can canonical the paginated series to it. For 600 posts with images, a View All page wrecks LCP and INP; keep paginated lists, self-canonical, with a sensible page size.&lt;/p&gt;

&lt;h2&gt;
  
  
  Author archives
&lt;/h2&gt;

&lt;p&gt;On a one-author blog, &lt;code&gt;/author/yourname/&lt;/code&gt; is an exact duplicate of &lt;code&gt;/blog/&lt;/code&gt;. That is the textbook thin hub.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Single-author site:&lt;/strong&gt; noindex the author archive (Yoast, Rank Math and SEOPress all have a toggle), or disable it and 301 it to an About page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Multi-author site:&lt;/strong&gt; keep author archives indexable &lt;em&gt;only&lt;/em&gt; if you add a real bio, expertise, photo and links to profiles. That supports E-E-A-T signals and gives the page unique value.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Watch for &lt;code&gt;/author/admin/&lt;/code&gt;.&lt;/strong&gt; It leaks your login username. Change the display name/slug, or disable the archive.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Date archives
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;/2024/&lt;/code&gt;, &lt;code&gt;/2024/03/&lt;/code&gt;, &lt;code&gt;/2024/03/15/&lt;/code&gt; almost never answer a search query. Nobody googles "your-site March 2024". For most small sites:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Noindex date archives (or disable them in your SEO plugin).&lt;/li&gt;
&lt;li&gt;Remove date archive widgets from the sidebar so you stop linking to them sitewide.&lt;/li&gt;
&lt;li&gt;Exception: news sites or diaries where chronology &lt;em&gt;is&lt;/em&gt; the content.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Parameter page= URLs
&lt;/h2&gt;

&lt;p&gt;You may also see &lt;code&gt;?page=2&lt;/code&gt;, &lt;code&gt;?paged=3&lt;/code&gt;, or &lt;code&gt;/page/2/?orderby=date&lt;/code&gt; from themes, filters or plugins. These create duplicate versions of the same list.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Make sure your theme outputs clean &lt;code&gt;/page/N/&lt;/code&gt; links.&lt;/li&gt;
&lt;li&gt;Canonical parameter versions to their clean equivalent.&lt;/li&gt;
&lt;li&gt;Do not block them in robots.txt if they already have canonicals; Google needs to crawl them to see the canonical.&lt;/li&gt;
&lt;li&gt;When sharing long filtered URLs in newsletters or social posts, a clean short link (try the free &lt;a href="https://riichimirza.com/tools/url-shortener/" rel="noopener noreferrer"&gt;URL shortener&lt;/a&gt;) keeps messy parameters out of circulation.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Infinite scroll and "Load more"
&lt;/h2&gt;

&lt;p&gt;Many modern block themes replace numbered pagination with a "Load more" button or infinite scroll. That is fine for users, but Googlebot does not click buttons or scroll to trigger fetches. If the only way to reach older posts is JavaScript, they effectively disappear from the crawl path. The fix is a hybrid: keep the JS experience, but make sure each chunk also exists at a real &lt;code&gt;/page/N/&lt;/code&gt; URL, and that a plain &lt;code&gt;&amp;lt;a href="/blog/page/2/"&amp;gt;&lt;/code&gt; link is present in the HTML (it can be visually replaced by the button). Test by disabling JavaScript in your browser: if you can still reach page 3, so can Google.&lt;/p&gt;

&lt;h2&gt;
  
  
  Titles and meta on paginated pages
&lt;/h2&gt;

&lt;p&gt;Page 2 of your blog often has the same title and meta description as page 1, which shows up as duplicate titles in audit tools. It is not a ranking problem, but it is easy to tidy. Most SEO plugins append "Page 2 of 9" automatically; check that the setting is on. Do not write unique, keyword-stuffed descriptions for every page of a list. A consistent pattern is enough.&lt;/p&gt;

&lt;h2&gt;
  
  
  What about category pagination?
&lt;/h2&gt;

&lt;p&gt;The same rules apply to &lt;code&gt;/category/x/page/2/&lt;/code&gt;. Category and tag thin archives are a separate topic, but if a category is indexable, its deeper pages should stay self-canonical and crawlable too. Do not noindex page 1 of a category while leaving page 2+ indexable; keep the series consistent.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common plugin settings, in plain words
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Yoast:&lt;/strong&gt; Settings &amp;gt; Advanced &amp;gt; Author archives / Date archives &amp;gt; toggle "Show in search results" off. Disabling the archive entirely redirects it to the homepage.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rank Math:&lt;/strong&gt; Titles &amp;amp; Meta &amp;gt; Authors / Misc Pages &amp;gt; set robots meta to noindex, or disable date archives.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SEOPress:&lt;/strong&gt; Titles &amp;amp; Metas &amp;gt; Archives &amp;gt; check noindex for author and date.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;After changing these, the plugin usually removes the archives from the XML sitemap automatically. Verify it by opening your sitemap index.&lt;/p&gt;

&lt;h2&gt;
  
  
  A 20-minute audit
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Run &lt;code&gt;site:yourdomain.com inurl:author&lt;/code&gt; and &lt;code&gt;site:yourdomain.com inurl:page&lt;/code&gt; in Google.&lt;/li&gt;
&lt;li&gt;In Search Console &amp;gt; Pages, filter for "Duplicate without user-selected canonical" and "Crawled – currently not indexed" and look for archive URLs.&lt;/li&gt;
&lt;li&gt;Check page 2 of your blog: view source, confirm the canonical points to itself.&lt;/li&gt;
&lt;li&gt;Set author (single-author) and date archives to noindex.&lt;/li&gt;
&lt;li&gt;Exclude noindexed archives from your XML sitemap.&lt;/li&gt;
&lt;li&gt;Bump posts per page and link evergreen posts from hubs.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Summary
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;rel=next is not a ranking lever; crawlable links and self-canonicals are.&lt;/li&gt;
&lt;li&gt;Keep pagination indexable unless you have a strong reason.&lt;/li&gt;
&lt;li&gt;Noindex single-author and date archives.&lt;/li&gt;
&lt;li&gt;Clean up page= parameters with canonicals, not robots.txt blocks.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;More practical WordPress SEO walkthroughs are on the &lt;a href="https://riichimirza.com/blog/" rel="noopener noreferrer"&gt;blog&lt;/a&gt;, and free utilities live on the &lt;a href="https://riichimirza.com/tools/" rel="noopener noreferrer"&gt;tools page&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>seo</category>
      <category>wordpress</category>
      <category>webdev</category>
      <category>beginners</category>
    </item>
    <item>
      <title>BreadcrumbList Hygiene and Thin Category/Tag Archives on Small WordPress Sites</title>
      <dc:creator>Riichi Mirza</dc:creator>
      <pubDate>Mon, 26 Oct 2026 23:11:31 +0000</pubDate>
      <link>https://dev.to/riichimirza/breadcrumblist-hygiene-and-thin-categorytag-archives-on-small-wordpress-sites-5111</link>
      <guid>https://dev.to/riichimirza/breadcrumblist-hygiene-and-thin-categorytag-archives-on-small-wordpress-sites-5111</guid>
      <description>&lt;p&gt;Breadcrumbs and taxonomy archives are the two parts of a small WordPress site nobody looks at after launch. Rank Math or Yoast turns breadcrumbs on, the theme prints its own trail, WordPress makes a category and tag archive for every term you have ever typed, and two years later you have a hundred thin archive URLs and a BreadcrumbList that doesn't match what people see on the page.&lt;/p&gt;

&lt;p&gt;None of this will sink a site on its own. Together, though, it means Google spends crawl time on pages that compete with your real posts, and your breadcrumb markup sends mixed signals about how the site is organised. This post is the cleanup I run on small sites. It isn't a Schema.org tutorial.&lt;/p&gt;

&lt;p&gt;2026 reality check: Google still reads BreadcrumbList, and it still shapes how your URL path looks in results, especially on desktop and in some surfaces where the breadcrumb label replaces the raw URL. Thin taxonomy archives still waste crawl budget and still get flagged as "Crawled – currently not indexed" in bulk. Both problems are boring, and both are still real.&lt;/p&gt;

&lt;h2&gt;
  
  
  Part 1: BreadcrumbList hygiene
&lt;/h2&gt;

&lt;h3&gt;
  
  
  One source of breadcrumbs, not three
&lt;/h3&gt;

&lt;p&gt;The most common problem is duplicates. The theme outputs a breadcrumb trail with microdata, Rank Math or Yoast outputs BreadcrumbList JSON-LD, and sometimes a page builder or WooCommerce adds a third. Google then sees two or three trails that disagree.&lt;/p&gt;

&lt;p&gt;How to check: open a post, view the source, and search for &lt;code&gt;BreadcrumbList&lt;/code&gt;. Then paste the URL into the Rich Results Test. If you see more than one BreadcrumbList item, pick one source:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Rank Math:&lt;/strong&gt; Settings → General → Breadcrumbs, then place the shortcode or block in your theme. Turn off the theme's own breadcrumbs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Yoast:&lt;/strong&gt; Settings → Advanced → Breadcrumbs. Yoast adds BreadcrumbList to its schema graph. Use its function or block for the visible trail and turn off the theme's.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Theme-only:&lt;/strong&gt; if you keep the theme's trail, make sure its markup is valid. Otherwise output it without markup and let the SEO plugin handle the schema.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The visible trail must match the JSON-LD
&lt;/h3&gt;

&lt;p&gt;Markup should describe what users see. Mismatches I see all the time:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The visible trail says &lt;code&gt;Home &amp;gt; Guides &amp;gt; Post&lt;/code&gt;, but the JSON-LD says &lt;code&gt;Home &amp;gt; Uncategorized &amp;gt; Post&lt;/code&gt;, because the plugin uses the first category alphabetically.&lt;/li&gt;
&lt;li&gt;A post sits in three categories, and the breadcrumb changes depending on which category was assigned first.&lt;/li&gt;
&lt;li&gt;Labels are different: the visible trail says "Blog", while the schema uses the page slug "blog-2".&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Fix: set a &lt;strong&gt;primary category&lt;/strong&gt; on every post (both Rank Math and Yoast let you do this in the category box). Rename or remove "Uncategorized". Give breadcrumb labels short human names that match your navigation.&lt;/p&gt;

&lt;h3&gt;
  
  
  Every item URL should be indexable and canonical
&lt;/h3&gt;

&lt;p&gt;Each &lt;code&gt;item&lt;/code&gt; in a BreadcrumbList should point to a URL that returns 200 and canonicalises to itself. Common problems:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A middle crumb points to a category archive you've set to noindex, or to a URL that redirects.&lt;/li&gt;
&lt;li&gt;The "Blog" crumb points to &lt;code&gt;/?page_id=12&lt;/code&gt; instead of &lt;code&gt;/blog/&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;The trail mixes &lt;code&gt;http&lt;/code&gt; and &lt;code&gt;https&lt;/code&gt;, or &lt;code&gt;www&lt;/code&gt; and non-&lt;code&gt;www&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If a crumb points to a URL you don't want indexed, either change the trail (skip that level) or make that level a real, useful hub page. When several URLs serve the same content, the rules from &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;fixing duplicate content with canonical tags&lt;/a&gt; apply here too: every crumb should use the one canonical version.&lt;/p&gt;

&lt;h3&gt;
  
  
  Keep the trail short and logical
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;Home &amp;gt; Category &amp;gt; Post&lt;/code&gt; is enough for most small sites. Don't fake depth with &lt;code&gt;Home &amp;gt; Blog &amp;gt; 2026 &amp;gt; October &amp;gt; SEO &amp;gt; Post&lt;/code&gt;. The last crumb can be the post title (Google ignores whether it has a link). Make sure the number of positions in the JSON-LD matches the number of crumbs people see.&lt;/p&gt;

&lt;h2&gt;
  
  
  Part 2: thin category and tag archives
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Why archives compete with posts
&lt;/h3&gt;

&lt;p&gt;WordPress creates &lt;code&gt;/category/x/&lt;/code&gt; and &lt;code&gt;/tag/y/&lt;/code&gt; automatically. On a site with 40 posts and 120 tags, most tag archives list one or two posts with the same excerpts. Google sees lots of near-duplicate pages, and for some queries a tag archive outranks (or cannibalises) the post it lists.&lt;/p&gt;

&lt;p&gt;Spot it in Google Search Console: Performance → Pages, filter by &lt;code&gt;/tag/&lt;/code&gt; or &lt;code&gt;/category/&lt;/code&gt;. Look for archive URLs getting impressions for queries that a specific post should own. Then check Pages → "Crawled – currently not indexed" for a pile of taxonomy URLs.&lt;/p&gt;

&lt;h3&gt;
  
  
  A simple noindex decision rule
&lt;/h3&gt;

&lt;p&gt;For each taxonomy term, ask:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Does it have at least 5–6 genuinely related posts?&lt;/strong&gt; If not, it's thin.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Would someone search for this term and be happy landing on the archive?&lt;/strong&gt; "WordPress SEO guides" maybe; "misc" or "tips2" no.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Does it have unique intro text?&lt;/strong&gt; A 100–200 word description that explains the topic and links to the best posts turns an archive into a real hub.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Then:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Categories that pass:&lt;/strong&gt; keep them indexed, add a description, and link to them from your menu or &lt;code&gt;/blog/&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tags:&lt;/strong&gt; for most small sites, noindex all tag archives (Rank Math: Titles &amp;amp; Meta → Tags; Yoast: Settings → Taxonomies → Tags → "Show tags in search results" off). Keep &lt;code&gt;follow&lt;/code&gt; so links still pass through.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Thin categories:&lt;/strong&gt; merge them. Move the posts into a stronger category and 301 the old archive URL to it. Noindex is the fallback, not the first choice.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Empty terms:&lt;/strong&gt; delete them.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Also remove noindexed archives from your XML sitemap. Both plugins do this automatically when you noindex a taxonomy type, but check anyway.&lt;/p&gt;

&lt;h3&gt;
  
  
  Pagination on archives
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;/category/seo/page/2/&lt;/code&gt; should canonicalise to &lt;strong&gt;itself&lt;/strong&gt;, not to page 1. Pointing every page at page 1 hides the posts on deeper pages. Keep paginated pages indexable if the category is indexable. Google no longer uses rel=next/prev, so the plain links between pages are what count. If a category runs to 15 pages, that's usually a sign to split it into subtopics or link to the deep posts from a hub, not to noindex pages 2 onwards.&lt;/p&gt;

&lt;p&gt;Date, author, and format archives on a one-author blog are pure duplication. Turn them off or noindex them.&lt;/p&gt;

&lt;h3&gt;
  
  
  Tidy the links you share
&lt;/h3&gt;

&lt;p&gt;When you share archive or hub links in newsletters or social posts, a clean short link (I use a &lt;a href="https://riichimirza.com/tools/url-shortener/" rel="noopener noreferrer"&gt;free URL shortener&lt;/a&gt;) keeps tracking parameters off your canonical URLs, so you don't create more variants for Google to sort out.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 10-minute recap
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;One breadcrumb source; theme trail off if the plugin handles it.&lt;/li&gt;
&lt;li&gt;Primary category set on every post; "Uncategorized" gone.&lt;/li&gt;
&lt;li&gt;Visible trail = JSON-LD trail, same labels and same depth.&lt;/li&gt;
&lt;li&gt;Every crumb URL returns 200, is canonical, and is indexable.&lt;/li&gt;
&lt;li&gt;Tag archives noindexed (follow kept) unless they're real hubs.&lt;/li&gt;
&lt;li&gt;Thin categories merged with a 301; empty terms deleted.&lt;/li&gt;
&lt;li&gt;Indexable categories have unique intro text.&lt;/li&gt;
&lt;li&gt;Paginated archives canonicalise to themselves.&lt;/li&gt;
&lt;li&gt;Date, author, and format archives off on single-author sites.&lt;/li&gt;
&lt;li&gt;Noindexed taxonomies are out of the sitemap.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;More small-site checklists are on &lt;a href="https://riichimirza.com/blog/" rel="noopener noreferrer"&gt;my blog&lt;/a&gt;, and free utilities are on the &lt;a href="https://riichimirza.com/tools/" rel="noopener noreferrer"&gt;tools page&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>seo</category>
      <category>wordpress</category>
      <category>webdev</category>
      <category>beginners</category>
    </item>
    <item>
      <title>FAQPage, HowTo, and LocalBusiness schema hygiene for small WordPress sites</title>
      <dc:creator>Riichi Mirza</dc:creator>
      <pubDate>Mon, 26 Oct 2026 23:00:23 +0000</pubDate>
      <link>https://dev.to/riichimirza/faqpage-howto-and-localbusiness-schema-hygiene-for-small-wordpress-sites-d5c</link>
      <guid>https://dev.to/riichimirza/faqpage-howto-and-localbusiness-schema-hygiene-for-small-wordpress-sites-d5c</guid>
      <description>&lt;p&gt;FAQ blocks, HowTo toggles, and LocalBusiness cards in Rank Math or Yoast feel like free rich results. On small WordPress sites they more often create &lt;strong&gt;invisible FAQPage spam&lt;/strong&gt;, &lt;strong&gt;the same FAQ JSON-LD on every URL&lt;/strong&gt;, &lt;strong&gt;HowTo markup on pages that are not procedures&lt;/strong&gt;, and &lt;strong&gt;LocalBusiness NAP that disagrees with the footer&lt;/strong&gt;. That is schema hygiene — not a Schema.org encyclopedia, not title/meta SERP copy, and not image/Open Graph cards. It is how you stop wasting structured-data credibility (and, where Google still shows enhancements, rich-result eligibility) on markup nobody can see or trust.&lt;/p&gt;

&lt;p&gt;Honest 2026 note up front: Google no longer shows FAQ or HowTo rich results for ordinary sites (HowTo deprecated earlier; FAQ rich results fully wound down in 2026). Leaving broken FAQ/HowTo on the page does not magically restore stars. Cleaning it still matters: GSC noise, other consumers, AI/answer surfaces that read markup, and the same plugin habits that spam FAQPage usually break &lt;strong&gt;LocalBusiness&lt;/strong&gt; — which still matters for local visibility. Fix the mistakes; do not chase dead SERP chrome.&lt;/p&gt;

&lt;h2&gt;
  
  
  What each type is for (no textbook)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;FAQPage:&lt;/strong&gt; a page whose primary content is a list of questions and answers visible to users. Markup should mirror visible Q&amp;amp;A — not a hidden accordion injected sitewide by a block.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;HowTo:&lt;/strong&gt; a page that teaches a real, ordered procedure with steps a human can follow. A service landing page (“We fix leaks in Austin”) is not a HowTo just because the plugin has a toggle.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;LocalBusiness (and subtypes):&lt;/strong&gt; who you are, where you operate, how to contact you. Name, address, phone (NAP), &lt;code&gt;url&lt;/code&gt;, and often &lt;code&gt;openingHours&lt;/code&gt; / &lt;code&gt;geo&lt;/code&gt; need to match what humans see. Wrong NAP is worse than sparse NAP.&lt;/p&gt;

&lt;p&gt;You do not need every Schema.org type enabled. You need &lt;strong&gt;visible FAQ only where the page is FAQ&lt;/strong&gt;, &lt;strong&gt;HowTo only on real procedures&lt;/strong&gt;, and &lt;strong&gt;one accurate LocalBusiness&lt;/strong&gt; that matches the site.&lt;/p&gt;

&lt;h2&gt;
  
  
  Myth: “Turn on the FAQ block everywhere for rich results”
&lt;/h2&gt;

&lt;p&gt;Rank Math FAQ blocks, Yoast FAQ blocks, and theme “SEO FAQ” widgets often emit &lt;code&gt;FAQPage&lt;/code&gt; JSON-LD even when the questions are collapsed, duplicated in a sidebar, or pasted into a reusable block that lands on Home, every service URL, and the blog index.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Problems:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Invisible or near-invisible FAQ (markup without matching visible content) fails Google’s own structured-data expectations and reads as spammy.&lt;/li&gt;
&lt;li&gt;The same five questions on thirty URLs create duplicate FAQ entities across the site.&lt;/li&gt;
&lt;li&gt;Editors keep adding keyword-stuffed “questions” nobody asks.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Prefer:&lt;/strong&gt; one dedicated FAQ URL (or a short visible FAQ section on a money page) with Q&amp;amp;A a human can read without opening DevTools. If the block is only there for JSON-LD, delete it.&lt;/p&gt;

&lt;p&gt;When the same FAQ copy appears on overlapping URLs, settle which URL owns the topic with &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;canonical tags&lt;/a&gt; — then keep FAQ markup on the &lt;strong&gt;canonical&lt;/strong&gt; page only.&lt;/p&gt;

&lt;h2&gt;
  
  
  Duplicate FAQ on every page
&lt;/h2&gt;

&lt;p&gt;Sitewide footer FAQs, “global” Rank Math snippets, and copied Gutenberg patterns are the usual source. View source (or the plugin’s schema preview) on Home, a service URL, and a blog post. If &lt;code&gt;FAQPage&lt;/code&gt; appears on all three with the same &lt;code&gt;@graph&lt;/code&gt; questions, that is not helpful coverage — it is duplication.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; remove global FAQ schema. Keep FAQ markup on pages whose &lt;em&gt;main&lt;/em&gt; content is Q&amp;amp;A. For a short on-page FAQ under a service guide, mark it up once on that URL; do not also emit it from the footer.&lt;/p&gt;

&lt;h2&gt;
  
  
  HowTo for non-howto pages
&lt;/h2&gt;

&lt;p&gt;“How we work” marketing copy, pricing tables, and “3 reasons to hire us” are not HowTo. Plugins that auto-wrap numbered lists as &lt;code&gt;HowTo&lt;/code&gt; create invalid or misleading graph nodes: missing &lt;code&gt;HowToStep&lt;/code&gt; text, steps that are slogans, or a single step that is the whole sales pitch.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prefer:&lt;/strong&gt; HowTo only when the page is literally instructional (replace a filter, submit a claim, configure a plugin). Otherwise leave the list as HTML. Do not enable HowTo sitewide “just in case.”&lt;/p&gt;

&lt;h2&gt;
  
  
  LocalBusiness NAP mismatches
&lt;/h2&gt;

&lt;p&gt;This is the type that still earns real attention for local businesses. Common small-site failures:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Symptom&lt;/th&gt;
&lt;th&gt;What breaks&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Plugin Name ≠ footer / GBP name&lt;/td&gt;
&lt;td&gt;Trust / entity confusion&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Address in schema, “serving Greater X” only in copy&lt;/td&gt;
&lt;td&gt;Inconsistent NAP&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Old phone in JSON-LD after a number change&lt;/td&gt;
&lt;td&gt;Call tracking / GBP mismatch&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Multiple LocalBusiness nodes (theme + Rank Math + directory plugin)&lt;/td&gt;
&lt;td&gt;Conflicting entities&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;url&lt;/code&gt; pointing at a campaign short link&lt;/td&gt;
&lt;td&gt;Wrong canonical home&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Campaign tracking can use a &lt;a href="https://riichimirza.com/tools/url-shortener/" rel="noopener noreferrer"&gt;URL shortener&lt;/a&gt;; &lt;strong&gt;LocalBusiness &lt;code&gt;url&lt;/code&gt; should be the stable homepage (or primary location URL)&lt;/strong&gt;, not a tagged short link. Align schema NAP with Google Business Profile and the visible footer before you chase more properties.&lt;/p&gt;

&lt;h2&gt;
  
  
  Missing required / expected properties
&lt;/h2&gt;

&lt;p&gt;FAQ without visible answers, HowTo without steps, LocalBusiness without &lt;code&gt;name&lt;/code&gt; + &lt;code&gt;address&lt;/code&gt; (and usually &lt;code&gt;telephone&lt;/code&gt; / &lt;code&gt;url&lt;/code&gt;) — validators complain for a reason. Adding twenty optional properties while &lt;code&gt;streetAddress&lt;/code&gt; is empty does not help. Fill the basics that match the page; skip vanity fields you cannot stand behind.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test with Rich Results Test (and friends)
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Pick money URLs: Home, top service/location page, real FAQ page (if any), one blog post.
&lt;/li&gt;
&lt;li&gt;Run &lt;a href="https://search.google.com/test/rich-results" rel="noopener noreferrer"&gt;Google Rich Results Test&lt;/a&gt; (and Search Console → Enhancements / structured data where reports still exist for types you use).
&lt;/li&gt;
&lt;li&gt;For FAQ/HowTo: treat “detected” as a hygiene signal, not a promise of FAQ stars in 2026. Remove spammy or invisible nodes anyway.
&lt;/li&gt;
&lt;li&gt;For LocalBusiness / Organization: fix errors and NAP mismatches until the graph matches the footer.
&lt;/li&gt;
&lt;li&gt;After plugin changes, re-test — caches and combined &lt;code&gt;@graph&lt;/code&gt; from two SEO plugins are common.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;One schema writer in &lt;code&gt;&amp;lt;head&amp;gt;&lt;/code&gt; beats Rank Math + Yoast + a theme “local SEO” pack racing the same types.&lt;/p&gt;

&lt;h2&gt;
  
  
  40-minute practical pass
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;List money URLs + any dedicated FAQ.
&lt;/li&gt;
&lt;li&gt;Search source for &lt;code&gt;FAQPage&lt;/code&gt; / &lt;code&gt;HowTo&lt;/code&gt; / &lt;code&gt;LocalBusiness&lt;/code&gt; — note which URLs emit them.
&lt;/li&gt;
&lt;li&gt;Kill invisible or sitewide duplicate FAQ blocks.
&lt;/li&gt;
&lt;li&gt;Strip HowTo from non-procedure pages.
&lt;/li&gt;
&lt;li&gt;Align LocalBusiness NAP with footer + GBP; one node.
&lt;/li&gt;
&lt;li&gt;Fill missing required basics; delete vanity junk.
&lt;/li&gt;
&lt;li&gt;Re-run Rich Results Test on what you changed.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Closing
&lt;/h2&gt;

&lt;p&gt;Small WordPress sites lose schema trust from &lt;strong&gt;FAQ blocks that spam invisible FAQPage&lt;/strong&gt;, &lt;strong&gt;duplicate FAQ on every URL&lt;/strong&gt;, &lt;strong&gt;HowTo on sales pages&lt;/strong&gt;, &lt;strong&gt;LocalBusiness NAP mismatches&lt;/strong&gt;, and &lt;strong&gt;missing required properties&lt;/strong&gt; — not from failing to enable every Schema.org type. Clean the graph so it describes visible content; put effort into LocalBusiness accuracy; stop expecting FAQ/HowTo SERP chrome that Google already retired.&lt;/p&gt;

&lt;p&gt;More practical technical notes: &lt;a href="https://riichimirza.com/blog/" rel="noopener noreferrer"&gt;blog&lt;/a&gt;. Free utilities when you need them: &lt;a href="https://riichimirza.com/tools/" rel="noopener noreferrer"&gt;tools&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;— Riichi Mirza&lt;/em&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>wordpress</category>
      <category>webdev</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Image SEO and Open Graph hygiene for small WordPress sites</title>
      <dc:creator>Riichi Mirza</dc:creator>
      <pubDate>Mon, 26 Oct 2026 22:48:42 +0000</pubDate>
      <link>https://dev.to/riichimirza/image-seo-and-open-graph-hygiene-for-small-wordpress-sites-4en2</link>
      <guid>https://dev.to/riichimirza/image-seo-and-open-graph-hygiene-for-small-wordpress-sites-4en2</guid>
      <description>&lt;p&gt;Image SEO and Open Graph hygiene are still how small WordPress sites get discovered in Google Images, earn a usable social preview when someone pastes a URL, and avoid shipping a theme screenshot as the public face of every share. They are not a full Core Web Vitals redo, not title/meta SERP copy, and not a substitute for &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;canonical tags&lt;/a&gt; when the wrong URL ranks. They are &lt;strong&gt;how media and previews describe the right page&lt;/strong&gt; so humans and crawlers are not left guessing from &lt;code&gt;IMG_4021.jpg&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;On sites under a few hundred URLs, the failure modes are boring and expensive: keyword-stuffed alts, missing width/height, multi‑megabyte heroes, OG titles that disagree with the page, the theme &lt;code&gt;screenshot.png&lt;/code&gt; as &lt;code&gt;og:image&lt;/code&gt;, useless filenames, and lazy-loading the above-fold hero. Fix those before you buy another “AI alt text” plugin.&lt;/p&gt;

&lt;h2&gt;
  
  
  What each piece actually does (no textbook)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Alt text:&lt;/strong&gt; accessible name when the image cannot be seen; also a relevance hint for image search. Describe honestly — do not dump the primary keyword five times.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Filename:&lt;/strong&gt; last path segment. Prefer readable slugs (&lt;code&gt;austin-leak-repair-before.jpg&lt;/code&gt;) over camera dumps. Name before upload when you can; renaming after is awkward in WordPress.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Width / height (or reserved aspect-ratio):&lt;/strong&gt; tell the browser how much room to keep. Missing dimensions invite CLS and make “huge hero” debugging harder.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Open Graph (&lt;code&gt;og:title&lt;/code&gt;, &lt;code&gt;og:description&lt;/code&gt;, &lt;code&gt;og:image&lt;/code&gt;, &lt;code&gt;og:url&lt;/code&gt;):&lt;/strong&gt; what Facebook, LinkedIn, Slack, iMessage, and many scrapers use. Twitter/X cards are adjacent. These are &lt;strong&gt;not&lt;/strong&gt; the Search title tag — align them; fixing one does not fix the other.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Featured / social image in SEO plugins:&lt;/strong&gt; Rank Math, Yoast, and friends often write OG from the featured image. Empty featured → sitewide default → or the theme screenshot.&lt;/p&gt;

&lt;p&gt;You do not need a DAM. You need money URLs with &lt;strong&gt;honest alts&lt;/strong&gt;, &lt;strong&gt;sane files&lt;/strong&gt;, &lt;strong&gt;dimensions&lt;/strong&gt;, and &lt;strong&gt;a real OG image that matches the page&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Myth: “Stuff keywords into every alt”
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;alt="plumber plumbing services best plumber Austin plumber near me"&lt;/code&gt; is not image SEO. Screen readers hear salad; image search gets a weak signal.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prefer:&lt;/strong&gt; &lt;code&gt;Emergency plumber tightening a shutoff valve under a kitchen sink in Austin&lt;/code&gt;&lt;br&gt;&lt;br&gt;
&lt;strong&gt;Avoid:&lt;/strong&gt; primary keyword ×5 with no visual description.&lt;/p&gt;

&lt;p&gt;Decorative chrome can use &lt;code&gt;alt=""&lt;/code&gt;. Content images — products, before/afters, diagrams — need real alts. Synonyms belong in captions and nearby copy, not as an alt stack.&lt;/p&gt;

&lt;h2&gt;
  
  
  Missing dimensions and oversized heroes (SEO first)
&lt;/h2&gt;

&lt;p&gt;Missing dimensions are usually framed as CLS. For small-site discoverability, the cousin problem is &lt;strong&gt;shipping a 4000px original as a 1200px hero&lt;/strong&gt; with no compression: users and scrapers pay, previews time out, and Image results prefer assets that actually load. Light LCP note only: a bloated above-fold hero is often the LCP element, so shrinking it helps CWV as a side effect — this wave stays about &lt;strong&gt;usable media and previews&lt;/strong&gt;, not a lab-score campaign.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Check&lt;/th&gt;
&lt;th&gt;Sensible target&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Hero display width&lt;/td&gt;
&lt;td&gt;Match layout (often ≤1200–1600 CSS px)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;File weight&lt;/td&gt;
&lt;td&gt;Well under ~200–300 KB when quality allows&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Format&lt;/td&gt;
&lt;td&gt;WebP/AVIF with fallback if needed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HTML dimensions&lt;/td&gt;
&lt;td&gt;width + height (or reserved aspect-ratio)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;One trusted optimizer beats five overlapping image plugins.&lt;/p&gt;

&lt;h2&gt;
  
  
  OG title / image mismatches
&lt;/h2&gt;

&lt;p&gt;Previews fail trust when &lt;code&gt;og:title&lt;/code&gt; still says “Home” on a service guide, &lt;code&gt;og:image&lt;/code&gt; is a logo-on-white for a before/after post, &lt;code&gt;og:description&lt;/code&gt; is the site tagline on every URL, or a 150×150 avatar is stretched into a 1.91:1 card.&lt;/p&gt;

&lt;p&gt;Scrapers cache hard. After edits, re-scrape money URLs in Facebook Sharing Debugger / LinkedIn Post Inspector (or equivalent). When two URLs overlap, settle the winner with &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;canonical tags&lt;/a&gt; first — then put the strong OG package on the &lt;strong&gt;canonical&lt;/strong&gt; URL.&lt;/p&gt;

&lt;h2&gt;
  
  
  Default theme screenshot as &lt;code&gt;og:image&lt;/code&gt;
&lt;/h2&gt;

&lt;p&gt;No featured image and no sitewide social default → theme &lt;code&gt;screenshot.png&lt;/code&gt; becomes every share card. Recipients see generic theme marketing, not your page. CTR from LinkedIn and Slack dies even when the URL is perfect.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fix:&lt;/strong&gt; set an explicit default OG image in your SEO plugin (brand-safe, ~1200×630, real photo or designed card). Override per money URL with a relevant featured/social image. Spot-check Home and top posts with a fresh scrape.&lt;/p&gt;

&lt;p&gt;Campaign links can use a &lt;a href="https://riichimirza.com/tools/url-shortener/" rel="noopener noreferrer"&gt;URL shortener&lt;/a&gt; for tracking; the &lt;strong&gt;destination&lt;/strong&gt; still needs correct &lt;code&gt;og:*&lt;/code&gt; tags. Do not assume the short link invents a good card.&lt;/p&gt;

&lt;h2&gt;
  
  
  Filename vs alt
&lt;/h2&gt;

&lt;p&gt;Related, not duplicates. &lt;strong&gt;Filename:&lt;/strong&gt; stable, lightly descriptive. &lt;strong&gt;Alt:&lt;/strong&gt; accessibility/description for this placement. &lt;strong&gt;Caption / nearby copy:&lt;/strong&gt; human context. Do not put the sales pitch in the filename. Do not leave &lt;code&gt;DSC_01992.JPG&lt;/code&gt; and hope a novel alt cancels it out. Same file in two posts may need two alts.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lazy-load pitfalls for above-fold
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;loading="lazy"&lt;/code&gt; on below-fold galleries is fine. Lazy on the &lt;strong&gt;hero / LCP image&lt;/strong&gt; delays first paint and muddies audits. WordPress and many themes auto-lazy content images; heroes often need an explicit &lt;strong&gt;not lazy&lt;/strong&gt; / &lt;code&gt;fetchpriority="high"&lt;/code&gt; path.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Hero: do &lt;strong&gt;not&lt;/strong&gt; lazy-load.
&lt;/li&gt;
&lt;li&gt;Give it dimensions.
&lt;/li&gt;
&lt;li&gt;Prefer sized srcset so mobile is not handed the desktop master.
&lt;/li&gt;
&lt;li&gt;Confirm OG image is an absolute HTTPS URL, not relative or localhost.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Discoverability footnote with a light performance edge — not a full INP/CLS program.&lt;/p&gt;

&lt;h2&gt;
  
  
  WordPress gotchas
&lt;/h2&gt;

&lt;p&gt;Two SEO plugins racing &lt;code&gt;og:image&lt;/code&gt;; page-builder background images with no alt; CDN offload breaking absolute OG URLs; mixed-content image URLs; Media Library re-uploads of the same photo under new names. Keep one head-tag writer. If the image carries meaning, use a real &lt;code&gt;&amp;lt;img&amp;gt;&lt;/code&gt; (or accessible text), not only CSS background.&lt;/p&gt;

&lt;h2&gt;
  
  
  35-minute practical pass
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;List money URLs.
&lt;/li&gt;
&lt;li&gt;Confirm &lt;code&gt;og:title&lt;/code&gt; / &lt;code&gt;og:image&lt;/code&gt; / &lt;code&gt;og:url&lt;/code&gt; — kill theme-screenshot defaults.
&lt;/li&gt;
&lt;li&gt;Heroes: weight, dimensions, not lazy.
&lt;/li&gt;
&lt;li&gt;Rewrite stuffed or empty content alts.
&lt;/li&gt;
&lt;li&gt;Name future uploads before Media Library.
&lt;/li&gt;
&lt;li&gt;Re-scrape OG on changed URLs.
&lt;/li&gt;
&lt;li&gt;Spot-check one share in Slack/iMessage if needed.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Closing
&lt;/h2&gt;

&lt;p&gt;Image SEO and Open Graph on small WordPress sites fail from &lt;strong&gt;alt stuffing&lt;/strong&gt;, &lt;strong&gt;missing dimensions&lt;/strong&gt;, &lt;strong&gt;oversized heroes&lt;/strong&gt;, &lt;strong&gt;OG mismatches&lt;/strong&gt;, &lt;strong&gt;theme-screenshot defaults&lt;/strong&gt;, &lt;strong&gt;useless filenames&lt;/strong&gt;, and &lt;strong&gt;lazy heroes&lt;/strong&gt; — not from missing an enterprise DAM. Ship media that loads, describes itself honestly, and previews as the page you meant to share.&lt;/p&gt;

&lt;p&gt;More practical technical notes: &lt;a href="https://riichimirza.com/blog/" rel="noopener noreferrer"&gt;blog&lt;/a&gt;. Free utilities when you need them: &lt;a href="https://riichimirza.com/tools/" rel="noopener noreferrer"&gt;tools&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;— Riichi Mirza&lt;/em&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>wordpress</category>
      <category>webdev</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Title tags and meta descriptions that actually help small WordPress sites</title>
      <dc:creator>Riichi Mirza</dc:creator>
      <pubDate>Mon, 26 Oct 2026 22:27:38 +0000</pubDate>
      <link>https://dev.to/riichimirza/title-tags-and-meta-descriptions-that-actually-help-small-wordpress-sites-423n</link>
      <guid>https://dev.to/riichimirza/title-tags-and-meta-descriptions-that-actually-help-small-wordpress-sites-423n</guid>
      <description>&lt;p&gt;Title tags and meta descriptions are still the first sales pitch most people see for a small WordPress site — in Google, Bing, and social previews that fall back to them. They are not Core Web Vitals, not soft-404 triage, and not a substitute for &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;canonical tags&lt;/a&gt; when the wrong URL is the one that ranks. They are &lt;strong&gt;how you label the right page&lt;/strong&gt; so humans click and search engines can match intent without guessing from a stuffed H1 alone.&lt;/p&gt;

&lt;p&gt;On sites under a few hundred URLs, the failure modes are boring and expensive: keyword stuffing that reads like spam, titles truncated mid-phrase in the SERP, every archive sharing the same auto title, blank metas that let Google invent a snippet from a random paragraph, and "clickbait" titles that mismatch the page and bounce the visit. Fix those before you buy another SERP-preview plugin.&lt;/p&gt;

&lt;h2&gt;
  
  
  What each field actually does (no textbook)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Title tag (&lt;code&gt;&amp;lt;title&amp;gt;&lt;/code&gt;):&lt;/strong&gt; primary label in the tab and usually the blue link in search results. Strong relevance signal + CTR lever. Unique per indexable URL when you can manage it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Meta description:&lt;/strong&gt; not a direct ranking factor in the classic sense, but it heavily influences whether someone clicks &lt;em&gt;your&lt;/em&gt; result vs a competitor. Google often rewrites it. Your job is to give a clear, honest candidate — not to game a character counter.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Open Graph / Twitter cards:&lt;/strong&gt; separate fields. Do not confuse them with title/meta for Search. Fix Search titles first on small sites; social can reuse good copy later.&lt;/p&gt;

&lt;p&gt;You do not need a brand book. You need every money URL to say &lt;strong&gt;what it is&lt;/strong&gt;, &lt;strong&gt;for whom&lt;/strong&gt;, and &lt;strong&gt;why open it&lt;/strong&gt; — in roughly one line.&lt;/p&gt;

&lt;h2&gt;
  
  
  Myth: "Stuff the primary keyword three times"
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;Best plumber plumber services plumber near me | Acme Plumbing Plumber&lt;/code&gt; does not "strengthen" relevance. It looks like spam to humans, truncates badly, and trains nobody to trust the brand. One clear primary phrase near the front is enough for small service and content sites. Synonyms belong in the body and H2s, not as a title stack.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prefer:&lt;/strong&gt; &lt;code&gt;Emergency plumber in Austin — same-day leak repair | Acme&lt;/code&gt;&lt;br&gt;&lt;br&gt;
&lt;strong&gt;Avoid:&lt;/strong&gt; keyword salad + pipe characters + city repeated four times.&lt;/p&gt;

&lt;p&gt;Keyword research still matters. Stuffing does not. Match the query the page can satisfy; do not invent density rituals from 2012 forum advice.&lt;/p&gt;

&lt;h2&gt;
  
  
  Myth: "Longer titles rank better" (and truncated SERP titles)
&lt;/h2&gt;

&lt;p&gt;SERP titles are truncated. Pixel width matters more than a magic 60-character rule, but &lt;strong&gt;~50–60 characters&lt;/strong&gt; is still a practical planning range for English desktop; mobile can cut earlier. Front-load the unique, useful part. Brand at the end unless the brand &lt;em&gt;is&lt;/em&gt; the query.&lt;/p&gt;

&lt;p&gt;Truncation patterns that waste CTR:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Pattern&lt;/th&gt;
&lt;th&gt;What users see&lt;/th&gt;
&lt;th&gt;Fix&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Important benefit after `&lt;/td&gt;
&lt;td&gt;Brand — long slogan`&lt;/td&gt;
&lt;td&gt;Benefit cut off&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;"How to … complete guide 2026 updated"&lt;/td&gt;
&lt;td&gt;"How to … complete g…"&lt;/td&gt;
&lt;td&gt;Cut filler words&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Duplicate prefix on every post&lt;/td&gt;
&lt;td&gt;"Blog — Blog — …"&lt;/td&gt;
&lt;td&gt;Kill sitewide title prefixes from themes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;City + service + city + service&lt;/td&gt;
&lt;td&gt;Mid-word cut on mobile&lt;/td&gt;
&lt;td&gt;One city, one service, brand&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Preview in an SEO plugin or a free SERP simulator, then &lt;strong&gt;read the truncated string out loud&lt;/strong&gt;. If the meaning dies at the ellipsis, rewrite.&lt;/p&gt;

&lt;h2&gt;
  
  
  Myth: "One title pattern for the whole site is fine"
&lt;/h2&gt;

&lt;p&gt;WordPress loves templates. Themes and SEO plugins often emit:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;%%title%% %%sep%% %%sitename%%&lt;/code&gt; on every post (fine if titles are unique)&lt;/li&gt;
&lt;li&gt;Category archives titled the same as the first post&lt;/li&gt;
&lt;li&gt;Tag, author, date, and pagination URLs with near-identical titles&lt;/li&gt;
&lt;li&gt;Homepage titled only the tagline, while &lt;code&gt;/emergency-plumber/&lt;/code&gt; is the money page&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Duplicate titles across archives do not "consolidate authority." They confuse which listing should earn the click and make GSC’s "Duplicate title tags" report noisy. For thin archives you may noindex; that is a robots/index decision, not a title decision. For archives you keep indexable, write distinct titles: &lt;code&gt;Plumbing tips archive | Acme&lt;/code&gt;, &lt;code&gt;Articles tagged “leak repair” | Acme&lt;/code&gt;, not the same string as the cornerstone guide.&lt;/p&gt;

&lt;p&gt;When two URLs fight because content overlaps, settle the URL with &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;canonical tags&lt;/a&gt; — then give the &lt;strong&gt;canonical&lt;/strong&gt; URL the strong title. Do not decorate the duplicate with a flashier title and hope.&lt;/p&gt;

&lt;h2&gt;
  
  
  Blank and auto-generated metas
&lt;/h2&gt;

&lt;p&gt;Blank meta descriptions invite Google to pull a random sentence — often a cookie notice, an author bio, or the middle of a list. Auto-generated metas that spit the first 160 characters of the post can work on tight intros and fail on waffle openings.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do this:&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Write a custom meta on every money URL (Home, service pages, top posts, contact/booking if indexed).
&lt;/li&gt;
&lt;li&gt;One or two sentences: problem → promise → proof or qualifier. No "Welcome to our website."
&lt;/li&gt;
&lt;li&gt;Include a natural entity or benefit; skip stuffing.
&lt;/li&gt;
&lt;li&gt;Aim ~140–160 characters as a planning range; accept that Google may rewrite.
&lt;/li&gt;
&lt;li&gt;If the plugin auto-fills from the excerpt, make the excerpt intentional — not leftover theme lorem.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Auto titles like &lt;code&gt;Untitled&lt;/code&gt; or &lt;code&gt;Auto Draft&lt;/code&gt; shipping to production still happen on small sites. Rank Math / Yoast / Slim SEO cannot save a blank post title. Editorial hygiene beats another toggle.&lt;/p&gt;

&lt;h2&gt;
  
  
  Writing for click + match (without clickbait)
&lt;/h2&gt;

&lt;p&gt;CTR without match is a bounce. Match without CTR is a missed impression. Good titles do both:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Specificity:&lt;/strong&gt; "Same-day drain clearing in North Austin" beats "Plumbing services."
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Honesty:&lt;/strong&gt; If the page is a checklist, say checklist — not "ultimate secret system."
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Query language:&lt;/strong&gt; Use the words people type when the page delivers that intent.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Differentiation:&lt;/strong&gt; One concrete outcome, audience, or constraint (price band, city, time, format).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Clickbait patterns that backfire on service SEO: fake urgency on evergreen pages, "number you won't believe," promising a free tool the page does not contain, or mismatching H1 vs title so badly users feel baited. Align H1 and title closely; they need not be identical, but they must describe the same document.&lt;/p&gt;

&lt;p&gt;Campaign links can use a &lt;a href="https://riichimirza.com/tools/url-shortener/" rel="noopener noreferrer"&gt;URL shortener&lt;/a&gt; for tracking; the destination still needs a SERP title that matches the landing promise.&lt;/p&gt;

&lt;h2&gt;
  
  
  WordPress-specific gotchas
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Homepage:&lt;/strong&gt; set an explicit SEO title; do not leave "Just another WordPress site."
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Brand sep:&lt;/strong&gt; short &lt;code&gt;|&lt;/code&gt; or &lt;code&gt;–&lt;/code&gt;; avoid stacking three seps.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CPTs / products:&lt;/strong&gt; audit one URL per template type.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pagination:&lt;/strong&gt; page 2+ must not clone page 1's title (or noindex per policy).
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One SEO plugin:&lt;/strong&gt; two writers in &lt;code&gt;&amp;lt;head&amp;gt;&lt;/code&gt; = race conditions.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  30-minute practical pass
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Export or screenshot GSC → Experience / HTML improvements (or crawl titles with a free crawler).
&lt;/li&gt;
&lt;li&gt;List money URLs; rewrite any stuffed, truncated-to-nonsense, or duplicate titles.
&lt;/li&gt;
&lt;li&gt;Front-load unique value; brand last.
&lt;/li&gt;
&lt;li&gt;Fill blank metas on money URLs; kill "Welcome to…" autos.
&lt;/li&gt;
&lt;li&gt;Spot-check category/tag/author titles for clones.
&lt;/li&gt;
&lt;li&gt;Preview mobile SERP truncation.
&lt;/li&gt;
&lt;li&gt;Align H1 with title intent.
&lt;/li&gt;
&lt;li&gt;Recrawl or Request indexing only for URLs you changed — patience on snippet updates.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Closing
&lt;/h2&gt;

&lt;p&gt;Title tags and meta descriptions on small WordPress sites fail from &lt;strong&gt;stuffing&lt;/strong&gt;, &lt;strong&gt;truncation&lt;/strong&gt;, &lt;strong&gt;duplicate archive templates&lt;/strong&gt;, &lt;strong&gt;blank/auto copy&lt;/strong&gt;, and &lt;strong&gt;clickbait mismatch&lt;/strong&gt; — not from missing a enterprise content hub. Write for a human skimming ten blue links: clear, front-loaded, honest, unique where it matters.&lt;/p&gt;

&lt;p&gt;More practical technical notes: &lt;a href="https://riichimirza.com/blog/" rel="noopener noreferrer"&gt;blog&lt;/a&gt;. Free utilities when you need them: &lt;a href="https://riichimirza.com/tools/" rel="noopener noreferrer"&gt;tools&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;— Riichi Mirza&lt;/em&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>wordpress</category>
      <category>webdev</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Core Web Vitals myths that waste time on small WordPress sites</title>
      <dc:creator>Riichi Mirza</dc:creator>
      <pubDate>Mon, 26 Oct 2026 22:12:08 +0000</pubDate>
      <link>https://dev.to/riichimirza/core-web-vitals-myths-that-waste-time-on-small-wordpress-sites-gk6</link>
      <guid>https://dev.to/riichimirza/core-web-vitals-myths-that-waste-time-on-small-wordpress-sites-gk6</guid>
      <description>&lt;p&gt;Page speed advice for small WordPress sites is drowning in lab scores and plugin upsells. Core Web Vitals matter — &lt;strong&gt;LCP&lt;/strong&gt;, &lt;strong&gt;INP&lt;/strong&gt;, and &lt;strong&gt;CLS&lt;/strong&gt; — but the myths around them burn more freelance hours than the metrics themselves. This is not an HTTPS padlock audit and not a soft-404 triage. It is &lt;strong&gt;what actually moves field data&lt;/strong&gt; on sites under a few hundred URLs: plugin bloat, image weight, render-blocking CSS/JS, and whether the host or the theme is the bottleneck.&lt;/p&gt;

&lt;p&gt;Lab tools (PageSpeed Insights desktop, Lighthouse local) are useful for triage. Field data (CrUX / GSC Core Web Vitals report) is what rankings care about when Google uses the signals. Optimize for both, but do not ship a 95 desktop lab score and ignore mobile field LCP on your money URL.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three metrics in one breath (no textbook)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;LCP (Largest Contentful Paint):&lt;/strong&gt; how fast the main visible thing appears — usually a hero image, H1 block, or big above-the-fold section. Slow LCP = heavy hero, late image, blocked CSS, cold TTFB from a cheap host.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;INP (Interaction to Next Paint):&lt;/strong&gt; how snappy the page feels after click/tap/key. Replaced FID. High INP = main-thread busy with fat JS (sliders, chat widgets, tag managers, page builders).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;CLS (Cumulative Layout Shift):&lt;/strong&gt; how much the layout jumps while loading. High CLS = images without dimensions, late web fonts, injected banners, cookie bars that shove content down.&lt;/p&gt;

&lt;p&gt;You do not need a PhD in performance timelines. You need to know which metric is red on the URL that makes money, then fix the cause class — not install a fifth "optimizer" plugin.&lt;/p&gt;

&lt;h2&gt;
  
  
  Myth: "Another speed plugin will fix CWV"
&lt;/h2&gt;

&lt;p&gt;Stacking cache + minify + lazyload + "AI optimize" + CDN plugins often &lt;strong&gt;adds&lt;/strong&gt; JS, doubles CSS processing, and fights the theme. On small sites the win is usually &lt;strong&gt;subtracting&lt;/strong&gt;, not stacking.&lt;/p&gt;

&lt;p&gt;Typical bloat pattern:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;What goes wrong&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Page builder + unused widgets&lt;/td&gt;
&lt;td&gt;Huge CSS/JS on every URL&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Three analytics + chat + heatmap&lt;/td&gt;
&lt;td&gt;Main-thread INP death&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Slider on every page "for branding"&lt;/td&gt;
&lt;td&gt;LCP image competition + JS&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Duplicate lazyload (theme + plugin + CDN)&lt;/td&gt;
&lt;td&gt;Broken images or late LCP&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;"Defer all JS" without testing&lt;/td&gt;
&lt;td&gt;Broken menus; INP looks fine until checkout&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Do this:&lt;/strong&gt; Inventory plugins that inject front-end assets. Disable one class at a time on staging (chat, sliders, unused builders). Keep one caching approach that your host understands. Measure mobile field or at least mobile lab on the money URL before/after — not Home only if Home is a brochure and &lt;code&gt;/contact/&lt;/code&gt; is the conversion page.&lt;/p&gt;

&lt;h2&gt;
  
  
  Myth: "Compress everything to WebP and LCP is solved"
&lt;/h2&gt;

&lt;p&gt;Image weight matters for LCP when the LCP element &lt;strong&gt;is&lt;/strong&gt; an image. If LCP is a text block waiting on render-blocking CSS, shrinking photos does little. If the hero is 4000px wide JPEG served full-bleed on mobile, you have an image problem.&lt;/p&gt;

&lt;p&gt;Practical image rules for small WP:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Resize before upload — do not rely on the browser to download 3MB and scale to 360px.&lt;/li&gt;
&lt;li&gt;Modern formats (WebP/AVIF) where the stack supports them; keep a sensible fallback.&lt;/li&gt;
&lt;li&gt;Width/height (or aspect-ratio) on &lt;code&gt;&amp;lt;img&amp;gt;&lt;/code&gt; to protect CLS.&lt;/li&gt;
&lt;li&gt;Priority / fetchpriority on the true LCP image; lazyload everything below the fold — &lt;strong&gt;not&lt;/strong&gt; the LCP image.&lt;/li&gt;
&lt;li&gt;Stop decorative carousels above the fold on money pages.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A &lt;a href="https://riichimirza.com/tools/url-shortener/" rel="noopener noreferrer"&gt;URL shortener&lt;/a&gt; for campaign links does not fix LCP. On-page media weight does.&lt;/p&gt;

&lt;h2&gt;
  
  
  Myth: "Render-blocking CSS/JS means eliminate all CSS"
&lt;/h2&gt;

&lt;p&gt;Browsers need CSS to paint. "Remove render-blocking resources" in Lighthouse often means: too much CSS before first paint, or JS in &lt;code&gt;&amp;lt;head&amp;gt;&lt;/code&gt; that could wait. Blindly deferring every stylesheet breaks above-the-fold layout (and can spike CLS when fonts/CSS arrive late).&lt;/p&gt;

&lt;p&gt;On WordPress:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Theme + builder + plugin CSS concatenated into a giant critical path&lt;/li&gt;
&lt;li&gt;Google Fonts loaded in a way that blocks or shifts text (FOIT/FOUT → CLS)&lt;/li&gt;
&lt;li&gt;Sync JS from tag managers in the head on every template&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Prefer:&lt;/strong&gt; critical CSS only if you can maintain it; otherwise reduce unused CSS (fewer plugins/builder modules), load non-critical JS deferred/async after measuring, self-host or subset fonts, and avoid injecting new head scripts "just to try." Settle which URL is canonical for testing the same way you settle &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;canonical tags&lt;/a&gt; when duplicates confuse which page to measure.&lt;/p&gt;

&lt;h2&gt;
  
  
  Host vs theme: who is guilty?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Host-leaning symptoms:&lt;/strong&gt; high TTFB, slow HTML document, good on-page weight but every URL feels cold, staging on the same plan is also slow, spikes at peak hours. Shared CPU limits and disk-bound PHP beat any minify plugin.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Theme/builder-leaning symptoms:&lt;/strong&gt; HTML arrives quickly but LCP/INP still red; Network waterfall shows huge CSS/JS; disabling the builder or a slider drops lab LCP hard; other sites on the same host are fine.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Both:&lt;/strong&gt; cheap host + heavy multipurpose theme + ten marketing pixels. Fix host enough that TTFB is boring, then cut front-end weight. Do not buy enterprise hosting to rescue a 2MB hero and three chat widgets.&lt;/p&gt;

&lt;p&gt;Quick split test: load the money URL with &lt;code&gt;?disable&lt;/code&gt; tricks or a staging clone with plugins off. If TTFB stays bad with a near-empty theme, talk to the host. If TTFB is fine and LCP/INP collapse with assets stripped, the theme/plugin stack owns it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Myth: "CLS is just ads — we don't run ads"
&lt;/h2&gt;

&lt;p&gt;Cookie consent, announcement bars, web fonts, embeds (maps, video), and images without dimensions shift layout on small service sites every day. CLS is not only display advertising.&lt;/p&gt;

&lt;p&gt;Fix order: dimensions on media, reserve space for consent banners (or load them without shoving H1), stable font loading (&lt;code&gt;font-display&lt;/code&gt;, subset), no late-injected headers that push content after first paint.&lt;/p&gt;

&lt;h2&gt;
  
  
  Myth: "Green PSI desktop = good CWV"
&lt;/h2&gt;

&lt;p&gt;Desktop lab on fiber is vanity. Google’s CWV for Search uses &lt;strong&gt;field&lt;/strong&gt; data, heavily mobile. A green desktop score with red mobile LCP on the URL in GSC is not success. Check GSC → Experience → Core Web Vitals (or CrUX) for the origin and, when available, specific URLs. Optimize the template that serves money traffic.&lt;/p&gt;

&lt;h2&gt;
  
  
  35-minute practical pass
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Note which metric is failing in GSC/CrUX (LCP, INP, CLS) for mobile.
&lt;/li&gt;
&lt;li&gt;Identify LCP element on the money URL (DevTools Performance / PSI screenshot).
&lt;/li&gt;
&lt;li&gt;If image: weight, dimensions, not lazy, sensible size. If text: CSS/font/TTFB path.
&lt;/li&gt;
&lt;li&gt;Count front-end injectors (chat, sliders, builders, tags); remove one unused class.
&lt;/li&gt;
&lt;li&gt;Check TTFB vs asset weight — host vs theme split.
&lt;/li&gt;
&lt;li&gt;Fix obvious CLS: img dimensions, font-display, banner space.
&lt;/li&gt;
&lt;li&gt;Re-test mobile lab; wait for field data to move (days/weeks).
&lt;/li&gt;
&lt;li&gt;Do not add a new optimizer plugin until something was removed.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Closing
&lt;/h2&gt;

&lt;p&gt;Core Web Vitals on small WordPress sites are usually &lt;strong&gt;plugin/theme weight&lt;/strong&gt;, &lt;strong&gt;image and font hygiene&lt;/strong&gt;, &lt;strong&gt;render-blocking excess&lt;/strong&gt;, and &lt;strong&gt;host TTFB&lt;/strong&gt; — not a missing enterprise RUM stack. Myths about stacking speed plugins, WebP-as-magic, deleting all CSS, and trusting desktop PSI waste the week you could have spent deleting one slider and resizing the hero.&lt;/p&gt;

&lt;p&gt;More practical technical notes: &lt;a href="https://riichimirza.com/blog/" rel="noopener noreferrer"&gt;blog&lt;/a&gt;. Free utilities when you need them: &lt;a href="https://riichimirza.com/tools/" rel="noopener noreferrer"&gt;tools&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;— Riichi Mirza&lt;/em&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>wordpress</category>
      <category>webdev</category>
      <category>performance</category>
    </item>
    <item>
      <title>HTTPS leftovers and mixed content mistakes that break small WordPress sites</title>
      <dc:creator>Riichi Mirza</dc:creator>
      <pubDate>Mon, 26 Oct 2026 21:59:25 +0000</pubDate>
      <link>https://dev.to/riichimirza/https-leftovers-and-mixed-content-mistakes-that-break-small-wordpress-sites-2i84</link>
      <guid>https://dev.to/riichimirza/https-leftovers-and-mixed-content-mistakes-that-break-small-wordpress-sites-2i84</guid>
      <description>&lt;p&gt;Installing SSL is the easy part. On small WordPress sites the broken padlock usually comes later: hard-coded &lt;code&gt;http://&lt;/code&gt; in the database, mixed active content, forms that still post to HTTP, and myths about admin-over-HTTP. This is not a redirect-chain audit and not a soft-404 triage. It is &lt;strong&gt;TLS leftovers after go-live&lt;/strong&gt; â€” what still loads insecurely, why Chrome complains, and which fixes are real.&lt;/p&gt;

&lt;p&gt;Redirects appear only where &lt;strong&gt;httpâ†’https single-hop hygiene&lt;/strong&gt; matters: one clean jump to HTTPS, then stop. Long chains belong to a different wave.&lt;/p&gt;

&lt;h2&gt;
  
  
  What "secure" actually means in the browser
&lt;/h2&gt;

&lt;p&gt;A green-ish padlock (or at least no "Not secure") means roughly:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The page URL is &lt;code&gt;https://&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;The certificate chain validates for that host&lt;/li&gt;
&lt;li&gt;No &lt;strong&gt;active&lt;/strong&gt; mixed content was allowed to run&lt;/li&gt;
&lt;li&gt;Forms that collect data do not submit to &lt;code&gt;http://&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Passive mixed content (images, video, audio) is discouraged and often warned&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Google can still crawl HTTP URLs. Users and Chrome treat them as second-class. Search prefers HTTPS when signals are equal; the practical win is trust, fewer warnings, and one canonical host scheme â€” settle scheme/host the same way you settle &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;canonical tags&lt;/a&gt; for duplicates.&lt;/p&gt;

&lt;h2&gt;
  
  
  HTTP leftovers after SSL (the WordPress tax)
&lt;/h2&gt;

&lt;p&gt;Freelancers often flip Let's Encrypt on, force HTTPS in Rank Math/Really Simple SSL, and call it done. The database still remembers the old world:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Leftover&lt;/th&gt;
&lt;th&gt;Symptom&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;siteurl&lt;/code&gt; / &lt;code&gt;home&lt;/code&gt; still &lt;code&gt;http://&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Admin loops, asset URLs wrong, mixed bag of schemes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Post content with hard-coded &lt;code&gt;http://yoursite.com/...&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Images/scripts break padlock on money pages&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Widget / Customizer CSS with absolute HTTP URLs&lt;/td&gt;
&lt;td&gt;Theme loads mixed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Old CDN / analytics snippet on &lt;code&gt;http://&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Active or passive mixed content&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Plugin options storing full HTTP asset URLs&lt;/td&gt;
&lt;td&gt;One plugin undoes the whole migration&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Email templates / PDF generators baking HTTP links&lt;/td&gt;
&lt;td&gt;Users land on HTTP, then bounce through a redirect&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Do this:&lt;/strong&gt; Settings â†’ General â†’ both addresses HTTPS. Dry-run DB search-replace for &lt;code&gt;http://yourdomain&lt;/code&gt; only â€” not every &lt;code&gt;http&lt;/code&gt; on the internet. Re-save permalinks once. Spot-check Home + money URLs in view-source for same-host &lt;code&gt;http://&lt;/code&gt; assets.&lt;/p&gt;

&lt;p&gt;External campaign links can still use a &lt;a href="https://riichimirza.com/tools/url-shortener/" rel="noopener noreferrer"&gt;URL shortener&lt;/a&gt;; on-site HTML and &lt;code&gt;siteurl&lt;/code&gt; should be HTTPS-only.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mixed content: active vs passive
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Passive (mostly display):&lt;/strong&gt; images, video, audio loaded over HTTP on an HTTPS page. Browsers may still show the page with a warning or block in stricter modes. Users see "Not fully secure."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Active (scripting / control):&lt;/strong&gt; scripts, stylesheets, iframes, XHR/fetch, WebSockets over HTTP on an HTTPS page. Modern browsers &lt;strong&gt;block&lt;/strong&gt; these. Your menu JS dies, your form validation vanishes, your pixel never fires â€” and the console fills with mixed-content errors.&lt;/p&gt;

&lt;p&gt;WordPress-specific active traps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Old jQuery or slider plugins still pointing at &lt;code&gt;http://&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Hotlinked third-party widgets that never upgraded&lt;/li&gt;
&lt;li&gt;Dusty child-theme font/icon kits on &lt;code&gt;http://&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Insecure iframes for maps, booking, or payment sandboxes&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Fix order:&lt;/strong&gt; DevTools â†’ Console / Security. List blocked URLs. Upgrade same-host assets to absolute HTTPS. Replace or remove third-party HTTP endpoints. Do not "fix" active mixed content by serving the page over HTTP again.&lt;/p&gt;

&lt;h2&gt;
  
  
  Insecure forms (the quiet conversion killer)
&lt;/h2&gt;

&lt;p&gt;Chrome flags pages where a form action targets &lt;code&gt;http://&lt;/code&gt; even if the page itself is HTTPS. Contact forms, newsletter boxes, login, checkout â€” anything that posts credentials or PII over cleartext earns a hard warning.&lt;/p&gt;

&lt;p&gt;Check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Form &lt;code&gt;action=&lt;/code&gt; attributes in the HTML (plugins love absolute URLs)&lt;/li&gt;
&lt;li&gt;AJAX endpoints that still call &lt;code&gt;admin-ajax.php&lt;/code&gt; via HTTP&lt;/li&gt;
&lt;li&gt;Payment or CRM embeds that open HTTP endpoints&lt;/li&gt;
&lt;li&gt;"Thank you" redirects that drop users onto HTTP (single hop back to HTTPS is hygiene; do not stack extras)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Cross-origin posts still need an HTTPS destination. There is no SEO prize for an insecure lead form.&lt;/p&gt;

&lt;h2&gt;
  
  
  Myth: "Never use wp-admin over HTTPS" / "Admin over HTTP is safer"
&lt;/h2&gt;

&lt;p&gt;You will still hear that SSL breaks admin, or that HTTP admin somehow avoids cookie theft.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reality:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Admin over HTTP sends cookies and passwords in cleartext on shared networks â€” the opposite of safer.&lt;/li&gt;
&lt;li&gt;Most "SSL broke my admin" tickets are &lt;strong&gt;mixed content or wrong &lt;code&gt;siteurl&lt;/code&gt;&lt;/strong&gt;, not TLS: HTTP assets in &lt;code&gt;/wp-admin/&lt;/code&gt;, a proxy missing &lt;code&gt;X-Forwarded-Proto&lt;/code&gt;, or a cached redirect loop.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;FORCE_SSL_ADMIN&lt;/code&gt; and host-level HTTPS for admin are normal, not exotic.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If admin breaks after SSL: private window, Console for mixed active content, verify &lt;code&gt;siteurl&lt;/code&gt;/&lt;code&gt;home&lt;/code&gt;, confirm the proxy tells PHP the request was HTTPS. Fix those before disabling HTTPS for admin "temporarily."&lt;/p&gt;

&lt;h2&gt;
  
  
  Real broken-padlock causes (frequency order on small WP)
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Hard-coded HTTP images in post content
&lt;/li&gt;
&lt;li&gt;Active mixed scripts from abandoned plugins
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;siteurl&lt;/code&gt; still HTTP or half-migrated
&lt;/li&gt;
&lt;li&gt;Insecure form actions
&lt;/li&gt;
&lt;li&gt;Third-party embeds stuck on HTTP
&lt;/li&gt;
&lt;li&gt;Service worker / cache serving old HTTP asset map
&lt;/li&gt;
&lt;li&gt;Certificate name mismatch (www vs apex) â€” different problem, same user panic
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Not on this list: "Google hates my H1" or "I need a longer redirect chain." Prefer &lt;strong&gt;one&lt;/strong&gt; 301 from HTTP to HTTPS on the final host. Apexâ†”www is a separate single choice. Multi-hop HTTPâ†’HTTPSâ†’wwwâ†’slash theater is redirect-wave territory â€” here the scheme hop just needs to be clean and immediate.&lt;/p&gt;

&lt;h2&gt;
  
  
  HSTS basics (lightly)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;HTTP Strict Transport Security&lt;/strong&gt; tells browsers: for this host, speak HTTPS only for a while (&lt;code&gt;max-age&lt;/code&gt;), optionally including subdomains, optionally preloadable.&lt;/p&gt;

&lt;p&gt;On small sites: enable HSTS &lt;strong&gt;after&lt;/strong&gt; HTTPS works everywhere you care about; start with a modest &lt;code&gt;max-age&lt;/code&gt;; use &lt;code&gt;includeSubDomains&lt;/code&gt; only if every real subdomain is ready; skip preload until you are sure. HSTS does not fix mixed content inside a page â€” it is a seatbelt after migration, not the migration itself.&lt;/p&gt;

&lt;h2&gt;
  
  
  30-minute hygiene pass
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Visit &lt;code&gt;http://yoursite.com&lt;/code&gt; â€” one hop to HTTPS? Same host you intend?
&lt;/li&gt;
&lt;li&gt;Settings â†’ General: both URLs HTTPS.
&lt;/li&gt;
&lt;li&gt;View-source Home + 3 money URLs: no same-host &lt;code&gt;http://&lt;/code&gt; assets.
&lt;/li&gt;
&lt;li&gt;DevTools Security/Console: zero active mixed content.
&lt;/li&gt;
&lt;li&gt;Submit a test contact form: action and AJAX over HTTPS.
&lt;/li&gt;
&lt;li&gt;Log into &lt;code&gt;/wp-admin/&lt;/code&gt; over HTTPS; Console clean.
&lt;/li&gt;
&lt;li&gt;Optional: enable HSTS at host/CDN once the above is green.
&lt;/li&gt;
&lt;li&gt;Spot-check GSC for leftover HTTP URLs; ensure internal links and sitemap entries use HTTPS.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Closing
&lt;/h2&gt;

&lt;p&gt;SSL is a certificate. &lt;strong&gt;HTTPS hygiene&lt;/strong&gt; is database URLs, asset schemes, forms, admin, and one clean httpâ†’https hop. Mixed active content breaks pages; insecure forms break trust; admin-over-HTTP myths break security. Fix leftovers before you rewrite copy.&lt;/p&gt;

&lt;p&gt;More practical technical notes: &lt;a href="https://riichimirza.com/blog/" rel="noopener noreferrer"&gt;blog&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;â€” Riichi Mirza&lt;/em&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>wordpress</category>
      <category>webdev</category>
      <category>beginners</category>
    </item>
    <item>
      <title>robots.txt and noindex mistakes that hide small WordPress sites</title>
      <dc:creator>Riichi Mirza</dc:creator>
      <pubDate>Mon, 26 Oct 2026 21:47:28 +0000</pubDate>
      <link>https://dev.to/riichimirza/robotstxt-and-noindex-mistakes-that-hide-small-wordpress-sites-50ca</link>
      <guid>https://dev.to/riichimirza/robotstxt-and-noindex-mistakes-that-hide-small-wordpress-sites-50ca</guid>
      <description>&lt;p&gt;On small WordPress sites, "Google won't index my pages" often traces back to two files of intent that contradict each other: &lt;code&gt;robots.txt&lt;/code&gt; and meta/&lt;code&gt;X-Robots-Tag&lt;/code&gt; noindex. This is not a soft-404 triage and not another sitemap hygiene rewrite. It is about &lt;strong&gt;access rules and index signals&lt;/strong&gt; — myths about blocking CSS/JS, real accidental &lt;code&gt;Disallow&lt;/code&gt; lines, noindex left in the sitemap, and staging leftovers that survived launch.&lt;/p&gt;

&lt;h2&gt;
  
  
  What each control actually does
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;&lt;code&gt;robots.txt&lt;/code&gt;&lt;/strong&gt; tells compliant crawlers which URL paths they may &lt;em&gt;fetch&lt;/em&gt;. A blocked URL can still appear in search (usually without a snippet) if Google found it another way. Blocking does &lt;strong&gt;not&lt;/strong&gt; reliably remove a URL from the index.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;code&gt;noindex&lt;/code&gt;&lt;/strong&gt; (meta robots or &lt;code&gt;X-Robots-Tag&lt;/code&gt;) tells Google not to &lt;em&gt;keep&lt;/em&gt; the URL in results — but Google must be able to &lt;strong&gt;fetch&lt;/strong&gt; the HTML (or headers) to see that tag. If &lt;code&gt;robots.txt&lt;/code&gt; blocks the URL, Google may never see your noindex.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sitemap&lt;/strong&gt; is a discovery wishlist. Putting a &lt;code&gt;noindex&lt;/code&gt; URL in the sitemap is mixed messaging: "please crawl this" + "please don't index this."&lt;/p&gt;

&lt;p&gt;Get those three straight before you rewrite plugins.&lt;/p&gt;

&lt;h2&gt;
  
  
  Myth: "You must Allow all CSS and JS or Google can't render"
&lt;/h2&gt;

&lt;p&gt;Google has asked for years not to block CSS/JS needed for rendering. That advice is still sound. The myth is the &lt;strong&gt;panic over-correction&lt;/strong&gt;: people paste giant &lt;code&gt;Allow:&lt;/code&gt; lists, open &lt;code&gt;/wp-includes/&lt;/code&gt; wholesale when nothing was blocked, or blame every indexation lag on a missing Allow rule.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reality on modern small WordPress sites:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Default WordPress &lt;code&gt;robots.txt&lt;/code&gt; usually only disallows &lt;code&gt;/wp-admin/&lt;/code&gt; (with &lt;code&gt;Allow&lt;/code&gt; for &lt;code&gt;admin-ajax.php&lt;/code&gt;) plus whatever you or a security plugin added.&lt;/li&gt;
&lt;li&gt;If Google can load your public CSS/JS from &lt;code&gt;/wp-content/&lt;/code&gt; and &lt;code&gt;/wp-includes/&lt;/code&gt; already, you do not need a novel Allow liturgy.&lt;/li&gt;
&lt;li&gt;Rendering problems that matter look like: blocked theme assets under a custom path, a WAF/&lt;code&gt;Disallow: /*.css$&lt;/code&gt; "security" rule, or a CDN path you accidentally disallowed.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Do this instead:&lt;/strong&gt; Fetch &lt;code&gt;https://yoursite.com/robots.txt&lt;/code&gt;. Search for &lt;code&gt;Disallow&lt;/code&gt; lines that hit &lt;code&gt;/wp-content/&lt;/code&gt;, &lt;code&gt;/wp-includes/&lt;/code&gt;, theme folders, or &lt;code&gt;*.css&lt;/code&gt; / &lt;code&gt;*.js&lt;/code&gt;. Remove those. Confirm in GSC URL Inspection → "Page resources" / screenshot that CSS/JS load. Skip cargo-cult Allow blocks if nothing was blocked.&lt;/p&gt;

&lt;h2&gt;
  
  
  Real accidental Disallow (the ones that actually hurt)
&lt;/h2&gt;

&lt;p&gt;I see these more often than CSS myths:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Pattern&lt;/th&gt;
&lt;th&gt;What happens&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;Disallow: /&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Whole site fetch-blocked for that user-agent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;Disallow: /*&lt;/code&gt; or over-broad &lt;code&gt;Disallow: /*?&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Query URLs, sometimes more than you meant&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Staging copy-paste: &lt;code&gt;Disallow: /&lt;/code&gt; left after go-live&lt;/td&gt;
&lt;td&gt;Production never gets crawled cleanly&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Security plugin: block &lt;code&gt;/author/&lt;/code&gt;, &lt;code&gt;/feed/&lt;/code&gt;, search, &lt;em&gt;and&lt;/em&gt; random asset paths&lt;/td&gt;
&lt;td&gt;Mixed — some OK, some break render&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;Disallow: /wp-content/uploads/&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;PDFs/images Google needed stop being fetched&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Manual "hide /blog/ while redesigning" forgotten&lt;/td&gt;
&lt;td&gt;Money content stays blocked for months&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;WordPress Settings → &lt;strong&gt;Reading → "Discourage search engines from indexing this site"&lt;/strong&gt; writes a sitewide discouragement (effectively treating the site as non-indexable via robots output / meta depending on setup). Freelancers flip it on for staging, migrate the database, and forget. Check it on every launch.&lt;/p&gt;

&lt;p&gt;Also check &lt;strong&gt;hosting panel robots&lt;/strong&gt;, &lt;strong&gt;CDN edge robots&lt;/strong&gt;, and a second &lt;code&gt;robots.txt&lt;/code&gt; served from a reverse proxy. What you edit in Rank Math is not always what &lt;code&gt;curl -I https://yoursite.com/robots.txt&lt;/code&gt; returns.&lt;/p&gt;

&lt;h2&gt;
  
  
  noindex mistakes on small WP installs
&lt;/h2&gt;

&lt;p&gt;Common, boring, expensive:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Category / tag / author archives set to noindex while you still want a hub category indexed&lt;/li&gt;
&lt;li&gt;Search (&lt;code&gt;/?s=&lt;/code&gt;), thank-you, cart, account — correctly noindex, but also left &lt;strong&gt;in&lt;/strong&gt; the XML sitemap&lt;/li&gt;
&lt;li&gt;"Noindex this post" used as a soft delete, then the URL stays published and linked&lt;/li&gt;
&lt;li&gt;Sitewide noindex from a maintenance / coming-soon plugin that was "turned off" in the UI but still injects headers&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;X-Robots-Tag: noindex&lt;/code&gt; on the whole host from staging server config (Apache/Nginx) after DNS cutover&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Rule:&lt;/strong&gt; noindex utility and thin archives on purpose. Do not noindex the five pages that pay rent. Do not leave noindex on URLs you still list in the sitemap and promote on the &lt;a href="https://riichimirza.com/blog/" rel="noopener noreferrer"&gt;blog&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conflicting noindex + sitemap
&lt;/h2&gt;

&lt;p&gt;If a URL is &lt;code&gt;noindex&lt;/code&gt;, remove it from the sitemap (or fix the plugin so those post types/archives are excluded). If you want it indexed, remove noindex and make sure it is fetchable and linked.&lt;/p&gt;

&lt;p&gt;GSC often shows &lt;strong&gt;Excluded by 'noindex' tag&lt;/strong&gt; next to URLs you are still "submitting." That is not a Google bug. Your stack is arguing with itself. Same class of confusion as duplicate URL variants — settle the intended URL with clear &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;canonical tags&lt;/a&gt; once fetch + index signals agree.&lt;/p&gt;

&lt;h2&gt;
  
  
  Staging leftovers (the migration tax)
&lt;/h2&gt;

&lt;p&gt;Staging is where robots/noindex debt is born:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;code&gt;Discourage search engines&lt;/code&gt; on&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;Disallow: /&lt;/code&gt; in robots&lt;/li&gt;
&lt;li&gt;Basic auth (password) — crawlers get 401, not your carefully written noindex&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;noindex,nofollow&lt;/code&gt; in the theme header "just in case"&lt;/li&gt;
&lt;li&gt;Sitemap still submitted for &lt;code&gt;staging.example.com&lt;/code&gt; in a leftover GSC property&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;After go-live checklist (15 minutes):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Reading setting: discouragement &lt;strong&gt;off&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;[ ] Live &lt;code&gt;robots.txt&lt;/code&gt;: no sitewide Disallow; keep &lt;code&gt;/wp-admin/&lt;/code&gt; pattern; Sitemap line points at &lt;strong&gt;production&lt;/strong&gt; HTTPS&lt;/li&gt;
&lt;li&gt;[ ] View-source on Home + one money URL: no &lt;code&gt;noindex&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;[ ] Response headers: no sitewide &lt;code&gt;X-Robots-Tag: noindex&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;[ ] GSC: production property verified; staging sitemap submissions removed or property ignored&lt;/li&gt;
&lt;li&gt;[ ] Internal links and shares use final production URLs (campaign links can use a &lt;a href="https://riichimirza.com/tools/url-shortener/" rel="noopener noreferrer"&gt;URL shortener&lt;/a&gt; externally — do not leave staging hosts in on-site hrefs)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Password protection blocks fetch; robots Disallow blocks fetch; noindex requires fetch. Pick one intentional strategy for staging — preferably auth or IP allowlist — and strip all of it on production.&lt;/p&gt;

&lt;h2&gt;
  
  
  A sane default for ~50–200 URL WordPress sites
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight conf"&gt;&lt;code&gt;&lt;span class="n"&gt;User&lt;/span&gt;-&lt;span class="n"&gt;agent&lt;/span&gt;: *
&lt;span class="n"&gt;Disallow&lt;/span&gt;: /&lt;span class="n"&gt;wp&lt;/span&gt;-&lt;span class="n"&gt;admin&lt;/span&gt;/
&lt;span class="n"&gt;Allow&lt;/span&gt;: /&lt;span class="n"&gt;wp&lt;/span&gt;-&lt;span class="n"&gt;admin&lt;/span&gt;/&lt;span class="n"&gt;admin&lt;/span&gt;-&lt;span class="n"&gt;ajax&lt;/span&gt;.&lt;span class="n"&gt;php&lt;/span&gt;

&lt;span class="n"&gt;Sitemap&lt;/span&gt;: &lt;span class="n"&gt;https&lt;/span&gt;://&lt;span class="n"&gt;www&lt;/span&gt;.&lt;span class="n"&gt;example&lt;/span&gt;.&lt;span class="n"&gt;com&lt;/span&gt;/&lt;span class="n"&gt;sitemap_index&lt;/span&gt;.&lt;span class="n"&gt;xml&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Add Disallow lines only when you can name the path and the reason (e.g. a private folder). Prefer &lt;strong&gt;noindex&lt;/strong&gt; for thank-you pages and thin archives you still need humans to open. Prefer &lt;strong&gt;removal + 404/410 or login&lt;/strong&gt; for content that should not exist publicly.&lt;/p&gt;

&lt;p&gt;Do not use robots.txt as a security boundary. Do not use noindex as a substitute for authentication.&lt;/p&gt;

&lt;h2&gt;
  
  
  25-minute audit habit
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open live robots.txt; list every Disallow; delete accidents.
&lt;/li&gt;
&lt;li&gt;Confirm CSS/JS for the theme are not disallowed.
&lt;/li&gt;
&lt;li&gt;View-source Home + top 5 money URLs for robots meta.
&lt;/li&gt;
&lt;li&gt;Spot-check headers for &lt;code&gt;X-Robots-Tag&lt;/code&gt;.
&lt;/li&gt;
&lt;li&gt;In the SEO plugin: which archives are noindex? Intentional?
&lt;/li&gt;
&lt;li&gt;Diff: noindex URLs vs sitemap children — remove conflicts.
&lt;/li&gt;
&lt;li&gt;Confirm Reading → discourage is off.
&lt;/li&gt;
&lt;li&gt;In GSC Coverage/Pages: sample "Blocked by robots.txt" and "Excluded by noindex" — fix causes, skip mass re-request as the only move.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Closing
&lt;/h2&gt;

&lt;p&gt;Small sites rarely need clever robots gymnastics. They need &lt;strong&gt;fetchable HTML&lt;/strong&gt;, &lt;strong&gt;honest noindex on utility URLs only&lt;/strong&gt;, &lt;strong&gt;no staging leftovers&lt;/strong&gt;, and &lt;strong&gt;no sitemap entries that contradict noindex&lt;/strong&gt;. Fix the accidental Disallow before you rewrite content. Fix conflicting signals before you blame crawl budget.&lt;/p&gt;

&lt;p&gt;More practical technical notes: &lt;a href="https://riichimirza.com/blog/" rel="noopener noreferrer"&gt;blog&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;— Riichi Mirza&lt;/em&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>wordpress</category>
      <category>webdev</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Internal Links for Small WordPress Sites: Hubs, Orphans, and Links That Actually Help</title>
      <dc:creator>Riichi Mirza</dc:creator>
      <pubDate>Mon, 26 Oct 2026 21:07:23 +0000</pubDate>
      <link>https://dev.to/riichimirza/internal-links-for-small-wordpress-sites-hubs-orphans-and-links-that-actually-help-2be1</link>
      <guid>https://dev.to/riichimirza/internal-links-for-small-wordpress-sites-hubs-orphans-and-links-that-actually-help-2be1</guid>
      <description>&lt;p&gt;Sitemaps tell Google a URL exists. Internal links tell Google (and humans) that you still stand behind it. On small WordPress sites — under a few hundred URLs — that endorsement gap is where indexation stalls more often than "missing XML."&lt;/p&gt;

&lt;p&gt;This is not another sitemap rewrite. It is the link graph side: hub pages, orphan recovery, nav/footer bloat, and in-content anchors that help without looking like spam.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why small sites still get this wrong
&lt;/h2&gt;

&lt;p&gt;Enterprise playbooks push automated "link every post to every related post" plugins. Small sites copy that energy and end up with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A mega-footer that lists every service, city, and blog post&lt;/li&gt;
&lt;li&gt;A primary menu with 18 items and three dropdowns of thin pages&lt;/li&gt;
&lt;li&gt;Blog posts that never mention older, stronger URLs&lt;/li&gt;
&lt;li&gt;Money pages that only appear in the sitemap&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Google can discover an orphan from XML and still leave it under &lt;strong&gt;Discovered - currently not indexed&lt;/strong&gt; because nothing on your site vouches for it. Discovery ≠ endorsement.&lt;/p&gt;

&lt;h2&gt;
  
  
  Hub pages: one topic, many spokes
&lt;/h2&gt;

&lt;p&gt;A hub is a page that exists to organize and link a cluster: a category landing, a "guides" index, a service overview that points to subpages, or a pillar post that summarizes and links out.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Good hubs on small WordPress sites:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;One clear intent (e.g. "WordPress technical SEO notes," not "everything we ever wrote")&lt;/li&gt;
&lt;li&gt;5–15 contextual links to spoke pages that earn a click&lt;/li&gt;
&lt;li&gt;Short intro + scannable sections; not a dumping ground for every tag&lt;/li&gt;
&lt;li&gt;Updated when you publish a new spoke (add the link; do not only bump &lt;code&gt;lastmod&lt;/code&gt; on the hub)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Weak hubs:&lt;/strong&gt; auto-generated tag archives with two posts, "Resources" pages that are just a bullet list of affiliate URLs, or category pages with no intro and zero internal context beyond the loop.&lt;/p&gt;

&lt;p&gt;WordPress category archives can be hubs if you add a custom intro (Rank Math / Yoast category description, or a page that &lt;em&gt;is&lt;/em&gt; the hub and links into the category). Prefer a real page you control when the default archive is thin.&lt;/p&gt;

&lt;h2&gt;
  
  
  Orphan recovery (without a six-figure crawler)
&lt;/h2&gt;

&lt;p&gt;An orphan is a published, indexable URL with &lt;strong&gt;no internal links&lt;/strong&gt; from other indexable pages (nav, footer, in-content, related modules — none).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Find them cheaply:&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Export URLs you care about (sitemap children, or WP export of posts/pages).&lt;/li&gt;
&lt;li&gt;Crawl the site with Screaming Frog free tier (or crawl menus + last 30 posts manually on a tiny site).&lt;/li&gt;
&lt;li&gt;Diff: in sitemap / published, &lt;strong&gt;zero inlinks&lt;/strong&gt; from the crawl → orphan candidates.&lt;/li&gt;
&lt;li&gt;Drop thank-you, cart, account, and intentionally unlinked legal pages from the panic list.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;Fix pattern (pick one per orphan):&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Situation&lt;/th&gt;
&lt;th&gt;Action&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Strong page, just forgotten&lt;/td&gt;
&lt;td&gt;Add 1–3 contextual links from related hubs/posts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Thin / near-duplicate&lt;/td&gt;
&lt;td&gt;Merge into a stronger URL; 301 the weak one; update links&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Outdated, no traffic, no links&lt;/td&gt;
&lt;td&gt;Unpublish or noindex; remove from sitemap&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Money page&lt;/td&gt;
&lt;td&gt;Link from home, hub, and 2–3 relevant posts — not only the footer&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Do not "fix" orphans by dumping them all into the footer. That creates a different problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  Footer and nav bloat
&lt;/h2&gt;

&lt;p&gt;Sitewide links pass discovery, but they dilute relevance when every URL is "important."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Symptoms I see on audits:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Footer columns with 40+ links, half to city landing pages nobody updates&lt;/li&gt;
&lt;li&gt;Primary nav that includes Blog, every service, every location, Contact, and three CTAs&lt;/li&gt;
&lt;li&gt;"Useful links" widgets repeating the same URLs already in the menu&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Practical caps for small sites:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Primary nav: roughly 5–7 top-level items. Deeper pages live in hubs and in-content links.&lt;/li&gt;
&lt;li&gt;Footer: contact, legal, 1 hub, a few evergreen money URLs — not the whole sitemap.&lt;/li&gt;
&lt;li&gt;If a page only exists in the footer, ask whether it deserves a contextual mention somewhere above the fold on a relevant page.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Bloat also hurts humans. If visitors cannot find the three pages that make you money, the crawl path is probably messy too.&lt;/p&gt;

&lt;h2&gt;
  
  
  In-content anchors that help (without spam)
&lt;/h2&gt;

&lt;p&gt;The highest-signal internal links are &lt;strong&gt;in the body&lt;/strong&gt;, next to a reason to click.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Link when you mention a topic you already covered ("I walked through &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;canonical tags&lt;/a&gt; separately")&lt;/li&gt;
&lt;li&gt;Use descriptive anchors: "redirect audit checklist," not "click here" or exact-match stuffed phrases&lt;/li&gt;
&lt;li&gt;Prefer one strong link to the best URL over five links to near-duplicates&lt;/li&gt;
&lt;li&gt;Point to the &lt;strong&gt;final canonical&lt;/strong&gt; URL (HTTPS, correct host, no leftover redirect hop)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Don't:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Auto-link the first mention of every keyword sitewide&lt;/li&gt;
&lt;li&gt;Insert a "related posts" block that is pure title stuffing with no context&lt;/li&gt;
&lt;li&gt;Link the same money URL ten times in one article&lt;/li&gt;
&lt;li&gt;Point campaign or UTM variants from your own content — keep those for ads/email; on-site HTML should use clean URLs (a &lt;a href="https://riichimirza.com/tools/url-shortener/" rel="noopener noreferrer"&gt;URL shortener&lt;/a&gt; is fine for &lt;em&gt;external&lt;/em&gt; shares, not as your internal path)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Related-posts plugins are fine as a backstop. They are not a substitute for two thoughtful links in the paragraphs that readers actually finish.&lt;/p&gt;

&lt;h2&gt;
  
  
  A simple linking model for `50–150 URL sites
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Home&lt;/strong&gt; → top hubs + 2–3 money pages&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Each hub&lt;/strong&gt; → its spokes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Each new post&lt;/strong&gt; → at least one older relevant URL + its hub&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Money pages&lt;/strong&gt; → appear in nav &lt;em&gt;or&lt;/em&gt; hub &lt;em&gt;and&lt;/em&gt; get occasional in-content mentions&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Legal / utility&lt;/strong&gt; → footer only is OK&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;When you publish, spend two minutes on links before you spend twenty on social snippets. The graph compounds; the tweet does not.&lt;/p&gt;

&lt;h2&gt;
  
  
  WordPress gotchas
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Menus vs widgets vs block theme patterns.&lt;/strong&gt; Links live in several places; updating one menu does not fix an old footer pattern or a reusable block.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"Related posts" + tag clouds.&lt;/strong&gt; Tag clouds are often thin-doorway magnets. Prefer curated hubs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pagination and "next post."&lt;/strong&gt; Useful for readers; weak as the &lt;em&gt;only&lt;/em&gt; path to older money content.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hardcoded theme footers.&lt;/strong&gt; Child theme or a footer block you can edit without a deploy every time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Canonical mismatch.&lt;/strong&gt; If you link &lt;code&gt;/page/&lt;/code&gt; but the canonical is &lt;code&gt;/page&lt;/code&gt;, fix the links — do not hope the SEO plugin papers over a messy graph. Pair with solid self-canonicals when duplicates remain: &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;how to fix duplicate content with canonical tags&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  30-minute weekly habit
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open the last 3 published URLs.&lt;/li&gt;
&lt;li&gt;Confirm each links to a hub and at least one related older URL.&lt;/li&gt;
&lt;li&gt;Confirm each money page gained or kept a contextual inlink this month.&lt;/li&gt;
&lt;li&gt;Skim footer/nav — remove anything that has not earned a click in ages.&lt;/li&gt;
&lt;li&gt;Spot-check 5 "Discovered - not indexed" URLs in GSC: orphan? thin? wrong canonical?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That habit beats a once-a-year "internal linking project" that never ships.&lt;/p&gt;

&lt;h2&gt;
  
  
  Closing
&lt;/h2&gt;

&lt;p&gt;On small WordPress sites, internal links are not a ranking trick. They are how you tell crawlers and clients which pages still matter. Build a few honest hubs, recover real orphans with contextual links, keep nav/footer boring, and write in-content anchors like a human recommending the next useful page.&lt;/p&gt;

&lt;p&gt;More practical notes live on the &lt;a href="https://riichimirza.com/blog/" rel="noopener noreferrer"&gt;blog&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;— Riichi Mirza&lt;/em&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>webdev</category>
      <category>wordpress</category>
      <category>beginners</category>
    </item>
    <item>
      <title>XML Sitemaps and Indexation Triage for Small WordPress Sites</title>
      <dc:creator>Riichi Mirza</dc:creator>
      <pubDate>Mon, 26 Oct 2026 20:49:50 +0000</pubDate>
      <link>https://dev.to/riichimirza/xml-sitemaps-and-indexation-triage-for-small-wordpress-sites-3h2g</link>
      <guid>https://dev.to/riichimirza/xml-sitemaps-and-indexation-triage-for-small-wordpress-sites-3h2g</guid>
      <description>&lt;p&gt;When a small WordPress site stalls in Google Search Console, people usually blame crawl budget or soft 404s. Fair topics — but a quieter mess sits in plain sight: the XML sitemap.&lt;/p&gt;

&lt;p&gt;On sites under a few hundred URLs, the sitemap is often the clearest signal you give Google about which pages you still stand behind. When it is noisy — redirects, &lt;code&gt;noindex&lt;/code&gt; pages, wild &lt;code&gt;lastmod&lt;/code&gt; dates — you get the classic combo: &lt;strong&gt;sitemap coverage looks fine&lt;/strong&gt; while &lt;strong&gt;Discovered - currently not indexed&lt;/strong&gt; keeps growing.&lt;/p&gt;

&lt;p&gt;This is the triage I use on freelance audits. Soft 404s are a separate problem; here we stay on sitemap hygiene vs indexation status.&lt;/p&gt;

&lt;h2&gt;
  
  
  What an XML sitemap is (and is not)
&lt;/h2&gt;

&lt;p&gt;A sitemap is a list of URLs you are willing to have discovered and considered for indexing. It does &lt;strong&gt;not&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Force indexing&lt;/li&gt;
&lt;li&gt;Override a &lt;code&gt;noindex&lt;/code&gt; or robots block&lt;/li&gt;
&lt;li&gt;Fix thin or duplicate content&lt;/li&gt;
&lt;li&gt;Replace internal links&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Google uses it as a discovery and freshness hint. If the list is trustworthy, Google leans on it. If it is stuffed with junk, Google learns to ignore parts of it — or you waste crawl and review time on URLs that should never have been submitted.&lt;/p&gt;

&lt;p&gt;WordPress ships a built-in sitemap at &lt;code&gt;/wp-sitemap.xml&lt;/code&gt; (an index pointing to post, page, category, user, etc. children). Rank Math, Yoast, and similar plugins often replace or extend that. Either way, &lt;strong&gt;you own what ends up in the list.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The four statuses people confuse
&lt;/h2&gt;

&lt;p&gt;Name the problem in Search Console before "fixing the sitemap":&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Discovered - currently not indexed&lt;/strong&gt; — Known URL, crawl not prioritized. Common on new/thin/orphan pages.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Crawled - currently not indexed&lt;/strong&gt; — Fetched, then declined. Sitemap inclusion will not bully it in.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Excluded by ‘noindex’&lt;/strong&gt; — Fine if intentional; a bug if those URLs are still in the sitemap.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Alternate / Google chose different canonical&lt;/strong&gt; — List only the &lt;strong&gt;canonical&lt;/strong&gt; URL in the sitemap; pair with solid self-canonicals (&lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;write-up&lt;/a&gt;).&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Sitemap triage helps most with (1) and pollution around (3)/(4). It rarely unlocks (2) alone.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sitemap hygiene rules for small WordPress sites
&lt;/h2&gt;

&lt;p&gt;Treat the sitemap as a &lt;strong&gt;contract&lt;/strong&gt;: only URLs that should be indexable live here.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Include only:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Final, canonical URLs&lt;/li&gt;
&lt;li&gt;HTTP 200 responses&lt;/li&gt;
&lt;li&gt;Indexable pages (&lt;code&gt;index,follow&lt;/code&gt; — or at least not &lt;code&gt;noindex&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Pages you would still link to from a sensible hub&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Exclude:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Redirects (301/302 destinations belong in the list; the redirecting URL does not)&lt;/li&gt;
&lt;li&gt;404/410 and soft-error templates&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;noindex&lt;/code&gt; archives, thank-you pages, cart/checkout, account areas&lt;/li&gt;
&lt;li&gt;Parameterized and tracking variants&lt;/li&gt;
&lt;li&gt;Staging, attachment pages you do not want indexed, empty author archives&lt;/li&gt;
&lt;li&gt;Paginated archive URLs if your plugin dumps every &lt;code&gt;page/2&lt;/code&gt; style URL without a plan&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;On a 80-page brochure site, a clean sitemap might be 60–90 URLs. If yours is 400, ask why.&lt;/p&gt;

&lt;h2&gt;
  
  
  lastmod myths
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;lastmod&lt;/code&gt; is a hint that the URL changed. It is not a ranking boost and not a "ping Google harder" button.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Myths I keep hearing:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;em&gt;"Bump lastmod daily so Google recrawls."&lt;/em&gt; If the content did not change, you are training distrust. Some systems rewrite &lt;code&gt;lastmod&lt;/code&gt; to "now" on every sitemap regenerate. Turn that off.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;"Missing lastmod means Google won't crawl."&lt;/em&gt; False. Discovery still works; you just lose a useful freshness signal when you &lt;em&gt;do&lt;/em&gt; edit.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;"lastmod must match the HTTP Last-Modified header exactly."&lt;/em&gt; Nice when true; not a hard requirement. Consistency beats perfection.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Practical rule:&lt;/strong&gt; Update &lt;code&gt;lastmod&lt;/code&gt; when the meaningful content or primary intent of the page changes — not when you tweak a sidebar widget sitewide.&lt;/p&gt;

&lt;p&gt;In Rank Math / Yoast, check whether "include last modified" is on and whether bulk edits or migrations stamped every post with today's date. After a migration, it is often better to accept older accurate dates than a sitewide "updated today" lie.&lt;/p&gt;

&lt;h2&gt;
  
  
  Orphan URLs: sitemap vs internal links
&lt;/h2&gt;

&lt;p&gt;A URL can be in the sitemap and still be an &lt;strong&gt;orphan&lt;/strong&gt; for humans: nothing in the main nav, posts, or hubs links to it. Google can discover it from the sitemap and still park it under Discovered/Crawled-not-indexed because nothing else on your site vouches for it.&lt;/p&gt;

&lt;p&gt;Triage pattern:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Export sitemap URLs (or open each child sitemap).&lt;/li&gt;
&lt;li&gt;Crawl internal links (Screaming Frog free tier, or even a simple crawl of menus + recent posts).&lt;/li&gt;
&lt;li&gt;Diff: &lt;strong&gt;in sitemap, not linked&lt;/strong&gt; → either add internal links from a relevant hub, or remove from sitemap and reconsider publishing.&lt;/li&gt;
&lt;li&gt;Diff: &lt;strong&gt;linked, not in sitemap&lt;/strong&gt; → usually fine if indexable; add if it is a money page you want discovered quickly.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Sitemaps are a backstop for discovery. Internal links are the endorsement. Orphans need endorsement more than another resubmit.&lt;/p&gt;

&lt;h2&gt;
  
  
  GSC: "Discovered - currently not indexed" vs sitemap coverage
&lt;/h2&gt;

&lt;p&gt;These reports answer different questions.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sitemaps report&lt;/strong&gt; (Indexing → Sitemaps): "Did Google fetch my sitemap file(s), and how many discovered URLs from them?" High "discovered" counts feel comforting. They do not mean indexed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pages report&lt;/strong&gt; reasons: "What happened to URLs we know about?" A URL can be "discovered via sitemap" and still sit in Discovered-not-indexed for weeks.&lt;/p&gt;

&lt;p&gt;When you triage:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open Sitemaps — confirm the submitted index URL is the one WordPress/plugin actually serves (no stale Yoast URL after switching to Rank Math, no &lt;code&gt;sitemap.xml&lt;/code&gt; 404).&lt;/li&gt;
&lt;li&gt;Note &lt;strong&gt;discovered vs indexed&lt;/strong&gt; counts. A huge gap is normal on new sites; a gap that never moves on old thin URLs is a content/demand problem.&lt;/li&gt;
&lt;li&gt;In Pages, filter Discovered-not-indexed. Sample 10–20 URLs:

&lt;ul&gt;
&lt;li&gt;In sitemap? Should they be?&lt;/li&gt;
&lt;li&gt;Linked internally?&lt;/li&gt;
&lt;li&gt;Unique title/intent vs near-duplicates?&lt;/li&gt;
&lt;li&gt;Thin (tag archives, empty categories)?&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Fix the list and the links before you hit "Request indexing" on dozens of URLs. Manual requests do not scale and do not fix systemic junk.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Resubmitting the same bloated sitemap daily does nothing useful. Cleaning it once does.&lt;/p&gt;

&lt;h2&gt;
  
  
  WordPress-specific gotchas
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Multiple sitemap plugins.&lt;/strong&gt; Pick one source of truth; remove obsolete submissions from GSC.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Author / tag sitemaps.&lt;/strong&gt; Disable if those archives are thin near-duplicates; keep useful category hubs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CDN caching stale XML.&lt;/strong&gt; After URL cleanups, purge and refetch the sitemap URL.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Campaign variants.&lt;/strong&gt; Keep the sitemap on clean canonicals; use tidy share links (e.g. &lt;a href="https://riichimirza.com/tools/url-shortener/" rel="noopener noreferrer"&gt;URL shortener&lt;/a&gt;) without listing parameter URLs.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A 45-minute triage checklist
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Fetch your live sitemap index; list child sitemaps.&lt;/li&gt;
&lt;li&gt;Confirm every listed URL returns 200 and is the HTTPS canonical host.&lt;/li&gt;
&lt;li&gt;Spot-check 15 URLs for &lt;code&gt;noindex&lt;/code&gt; and unexpected canonicals.&lt;/li&gt;
&lt;li&gt;Disable author/tag (or other) sitemaps you do not want indexed.&lt;/li&gt;
&lt;li&gt;Turn off fake &lt;code&gt;lastmod&lt;/code&gt; bumping; verify a recently edited post shows a sensible date.&lt;/li&gt;
&lt;li&gt;Diff sitemap vs internal links; fix orphans or delist them.&lt;/li&gt;
&lt;li&gt;In GSC, remove obsolete sitemap submissions; keep one clean index.&lt;/li&gt;
&lt;li&gt;Improve or consolidate the worst Discovered/Crawled-not-indexed samples — then wait.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Closing
&lt;/h2&gt;

&lt;p&gt;Indexation problems on small WordPress sites are rarely solved by "adding a sitemap." Most already have one. Make it &lt;strong&gt;boring and honest&lt;/strong&gt;: final, indexable, linked URLs, with &lt;code&gt;lastmod&lt;/code&gt; that means something.&lt;/p&gt;

&lt;p&gt;When duplicates confuse GSC too, fix canonicals rather than hoping the sitemap wins: &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;how to fix duplicate content with canonical tags&lt;/a&gt;. More notes: &lt;a href="https://riichimirza.com/blog/" rel="noopener noreferrer"&gt;blog&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;— Riichi Mirza&lt;/em&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>webdev</category>
      <category>wordpress</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Redirect Chains on Small Sites: How Three Hops Quietly Waste Your Crawl and Your Users' Patience</title>
      <dc:creator>Riichi Mirza</dc:creator>
      <pubDate>Mon, 26 Oct 2026 20:35:05 +0000</pubDate>
      <link>https://dev.to/riichimirza/redirect-chains-on-small-sites-how-three-hops-quietly-waste-your-crawl-and-your-users-patience-126h</link>
      <guid>https://dev.to/riichimirza/redirect-chains-on-small-sites-how-three-hops-quietly-waste-your-crawl-and-your-users-patience-126h</guid>
      <description>&lt;p&gt;Most small-site owners I work with don't have a "redirect problem." They have a redirect &lt;em&gt;history&lt;/em&gt;. Every redesign, HTTPS migration, slug tidy-up and plugin swap left a rule behind, and nobody ever went back to flatten them. The result is redirect chains: one URL bouncing through two, three, sometimes five hops before a visitor (or Googlebot) reaches the real page.&lt;/p&gt;

&lt;p&gt;This post is the practical version: what a chain looks like, why it matters even on a 40-page site, the one pattern that does real damage (mass homepage redirects), and how to fix everything down to a single hop.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a redirect chain actually is
&lt;/h2&gt;

&lt;p&gt;A chain is any request that needs more than one redirect to resolve. A classic small-business example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="err"&gt;http://example.com/services
  → 301 https://example.com/services
  → 301 https://www.example.com/services
  → 301 https://www.example.com/services/
  → 200
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three hops for one page. Nobody planned that. The HTTPS rule came from the host, the www rule from a plugin, the trailing slash from WordPress permalinks. Each one is "correct" on its own. Together they're waste.&lt;/p&gt;

&lt;p&gt;A &lt;strong&gt;loop&lt;/strong&gt; is the nasty cousin: A → B → A. Browsers give up with "too many redirects," and so does Google.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it matters even on a small site
&lt;/h2&gt;

&lt;p&gt;You'll read that crawl budget only matters for million-page sites. Mostly true. But chains cost you in other ways:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Latency on every hop.&lt;/strong&gt; Each redirect is a fresh round trip — DNS (sometimes), TLS, server response. On mobile with a slow shared host, three hops can add close to a second before the first byte of real HTML.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Googlebot stops following eventually.&lt;/strong&gt; Google follows up to roughly 10 hops in one go, but long chains get deferred, and every hop is another chance for something to break.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Signal dilution and confusion.&lt;/strong&gt; A 301 passes signals, but chains mixed with 302s, meta refreshes or JavaScript redirects make it harder for Google to be sure which URL is canonical. That's how you end up with the "wrong" version indexed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Internal links point at old URLs.&lt;/strong&gt; Chains almost always mean your own menus, footers and posts still link to dead addresses. That's the part you fully control.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The pattern that does real damage: mass 301s to the homepage
&lt;/h2&gt;

&lt;p&gt;During a cleanup, a common shortcut is: "Redirect every deleted page to the homepage." It feels tidy. It isn't.&lt;/p&gt;

&lt;p&gt;Google treats a redirect from a specific page (say, an old product or blog post) to an unrelated homepage as a &lt;strong&gt;soft 404&lt;/strong&gt;. The old URL isn't credited as moved — it's treated as gone, but with extra confusion. You lose whatever relevance that old page had, and Search Console fills up with soft-404 reports you can't explain.&lt;/p&gt;

&lt;p&gt;The rule I use with clients:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Relevant replacement exists?&lt;/strong&gt; 301 to that exact page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Category or parent exists?&lt;/strong&gt; 301 to the closest parent (e.g. &lt;code&gt;/blog/&lt;/code&gt; for retired posts).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nothing relevant?&lt;/strong&gt; Let it return a real &lt;strong&gt;404 or 410&lt;/strong&gt;. That's honest, and it's fine.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The homepage should be a redirect target only for things that genuinely were the homepage (old &lt;code&gt;index.html&lt;/code&gt;, &lt;code&gt;/home&lt;/code&gt;, the non-www root).&lt;/p&gt;

&lt;h2&gt;
  
  
  How to find your chains (free, 20 minutes)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. curl one URL to see every hop&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-sIL&lt;/span&gt; http://example.com/services | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-iE&lt;/span&gt; &lt;span class="s2"&gt;"^(HTTP|location)"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You'll see each status code and &lt;code&gt;Location&lt;/code&gt; header in order. More than one 301 = chain.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Crawl the whole site&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Screaming Frog (free up to 500 URLs) → &lt;em&gt;Reports → Redirects → Redirect Chains&lt;/em&gt;. On a small site this gives you the full list in minutes. Any free crawler that reports "redirect chains" works.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Check Search Console&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Pages&lt;/em&gt; report → look at "Page with redirect" and "Soft 404." If the soft-404 list is full of old URLs, check whether they're redirecting to the homepage.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Check your redirect sources&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;On WordPress, chains usually come from three places stacked on each other: &lt;code&gt;.htaccess&lt;/code&gt; / server config, a redirect plugin (Redirection, Rank Math, Yoast Premium), and the host's own HTTPS/www setting. List what each one does before you change anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fixing chains down to a single hop
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Step 1 — Pick one canonical host format.&lt;/strong&gt; &lt;code&gt;https://www.&lt;/code&gt; or &lt;code&gt;https://&lt;/code&gt; without www, with or without trailing slash. Decide once.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 2 — Make the protocol + host redirect a single rule.&lt;/strong&gt; Instead of separate HTTP→HTTPS and non-www→www rules, combine them so any variant goes straight to the final form:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight apache"&gt;&lt;code&gt;&lt;span class="nc"&gt;RewriteEngine&lt;/span&gt; &lt;span class="ss"&gt;On&lt;/span&gt;
&lt;span class="nc"&gt;RewriteCond&lt;/span&gt; %{HTTPS} &lt;span class="ss"&gt;off&lt;/span&gt; [OR]
&lt;span class="nc"&gt;RewriteCond&lt;/span&gt; %{HTTP_HOST} !^www\. [NC]
&lt;span class="nc"&gt;RewriteRule&lt;/span&gt; ^(.*)$ https://www.example.com/$1 [L,R=301]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Turn off duplicate "force HTTPS" toggles in plugins or the host panel if this rule now handles it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 3 — Update old redirects to point at the final URL.&lt;/strong&gt; If &lt;code&gt;/old-page&lt;/code&gt; → &lt;code&gt;/new-page&lt;/code&gt; and later &lt;code&gt;/new-page&lt;/code&gt; → &lt;code&gt;/newest-page&lt;/code&gt;, edit the first rule so &lt;code&gt;/old-page&lt;/code&gt; → &lt;code&gt;/newest-page&lt;/code&gt; directly. Every redirect should land on a 200.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 4 — Fix internal links at the source.&lt;/strong&gt; Search your content and menus for old URLs and replace them with the final URL. Redirects are for outside links you can't control; your own links should never need one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 5 — Clean up homepage dumps.&lt;/strong&gt; Go through any bulk "everything → /" rules. Map each URL to a relevant page, a parent section, or let it 404/410.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 6 — Re-crawl and verify.&lt;/strong&gt; Run the crawler again. Target: zero chains, zero loops, every internal link returning 200 directly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Don't forget canonicals and sitemaps
&lt;/h2&gt;

&lt;p&gt;Redirects, canonical tags and sitemaps should all agree on the same final URL. If your sitemap lists &lt;code&gt;http://example.com/page&lt;/code&gt; and your canonical says &lt;code&gt;https://www.example.com/page/&lt;/code&gt;, you're sending mixed signals. I wrote a full walkthrough on getting canonicals consistent here: &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;How to fix duplicate content with canonical tags&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  A note on short links and campaign URLs
&lt;/h2&gt;

&lt;p&gt;Short links and QR codes are redirects too — usually one hop, which is fine. The problem is when the short link points at an old URL that &lt;em&gt;also&lt;/em&gt; redirects. Now a printed QR code on a flyer runs a three-hop chain forever. When you update a page's URL, update the destination of any short links pointing at it. A simple &lt;a href="https://riichimirza.com/tools/url-shortener/" rel="noopener noreferrer"&gt;URL shortener&lt;/a&gt; where you can edit destinations later saves you from this.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] One canonical host format, enforced by one rule&lt;/li&gt;
&lt;li&gt;[ ] No redirect points to another redirect&lt;/li&gt;
&lt;li&gt;[ ] No loops&lt;/li&gt;
&lt;li&gt;[ ] No mass 301s to the homepage for unrelated pages&lt;/li&gt;
&lt;li&gt;[ ] Internal links, sitemap and canonicals use final URLs&lt;/li&gt;
&lt;li&gt;[ ] Short links / QR destinations updated after URL changes&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Redirect cleanup isn't glamorous, but on a small site it's one of the few technical fixes you can finish completely in an afternoon. More practical small-site SEO notes on the &lt;a href="https://riichimirza.com/blog/" rel="noopener noreferrer"&gt;Riichi Mirza blog&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>seo</category>
      <category>webdev</category>
      <category>wordpress</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Canonical tags on small sites: when they help and when they hide indexing bugs</title>
      <dc:creator>Riichi Mirza</dc:creator>
      <pubDate>Mon, 26 Oct 2026 20:12:31 +0000</pubDate>
      <link>https://dev.to/riichimirza/canonical-tags-on-small-sites-when-they-help-and-when-they-hide-indexing-bugs-4lkj</link>
      <guid>https://dev.to/riichimirza/canonical-tags-on-small-sites-when-they-help-and-when-they-hide-indexing-bugs-4lkj</guid>
      <description>&lt;p&gt;Most small sites I audit as a freelancer have canonical tags. Very few have &lt;em&gt;correct&lt;/em&gt; canonical tags. And the bad ones rarely throw an error — they just quietly tell Google "don't index this page," and you find out three months later when a page you care about shows up in Search Console as &lt;strong&gt;"Alternate page with proper canonical tag"&lt;/strong&gt; or &lt;strong&gt;"Duplicate, Google chose different canonical than user."&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This post is about the practical middle ground: when a canonical tag genuinely helps a 20–200 page site, and when it's papering over a bug you should fix instead.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a canonical tag actually does
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;&amp;lt;link rel="canonical" href="https://example.com/page/"&amp;gt;&lt;/code&gt; is a &lt;strong&gt;hint&lt;/strong&gt;, not a directive. You're telling search engines: "if you find several versions of this content, this URL is the one I want shown."&lt;/p&gt;

&lt;p&gt;Google weighs it alongside other signals: internal links, sitemaps, redirects, HTTPS, and which URL other sites link to. If those signals disagree with your canonical, Google may ignore it. That's the part most people miss.&lt;/p&gt;

&lt;h2&gt;
  
  
  When canonicals genuinely help on small sites
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Tracking and campaign parameters.&lt;/strong&gt;&lt;br&gt;
&lt;code&gt;/pricing/?utm_source=newsletter&lt;/code&gt; and &lt;code&gt;/pricing/&lt;/code&gt; are the same page. A self-referencing canonical on &lt;code&gt;/pricing/&lt;/code&gt; consolidates them. This matters a lot if you share links through a shortener or QR codes — every campaign URL with parameters is a potential duplicate. (If you build tagged links with a tool like the &lt;a href="https://riichimirza.com/tools/url-shortener/" rel="noopener noreferrer"&gt;free URL shortener on my site&lt;/a&gt;, the destination still needs a clean self-canonical, or you'll scatter signals across parameter variants.)&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Sorting and filtering.&lt;/strong&gt;&lt;br&gt;
&lt;code&gt;/shop/?sort=price&lt;/code&gt; and &lt;code&gt;/shop/?sort=newest&lt;/code&gt; show the same products. Canonical both to &lt;code&gt;/shop/&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Syndicated content.&lt;/strong&gt;&lt;br&gt;
If you republish an article on DEV, Medium, or Hashnode, a cross-domain canonical back to the original tells Google which version is primary.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Print / AMP / alternate templates.&lt;/strong&gt;&lt;br&gt;
Legacy setups that generate parallel versions of the same page.&lt;/p&gt;

&lt;p&gt;In all four cases, the duplicate &lt;em&gt;should&lt;/em&gt; exist for users, but shouldn't compete in search.&lt;/p&gt;
&lt;h2&gt;
  
  
  When canonicals hide indexing bugs
&lt;/h2&gt;

&lt;p&gt;Here's where I see trouble.&lt;/p&gt;
&lt;h3&gt;
  
  
  Bug 1: Canonical used instead of a redirect
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;http://&lt;/code&gt; vs &lt;code&gt;https://&lt;/code&gt;, &lt;code&gt;www&lt;/code&gt; vs non-&lt;code&gt;www&lt;/code&gt;, trailing slash vs none. If both versions return 200 and you rely on the canonical to sort it out, you're leaking crawl and link signals. &lt;strong&gt;These should be 301 redirects.&lt;/strong&gt; A canonical is for duplicates that need to stay accessible; a redirect is for duplicates that shouldn't exist.&lt;/p&gt;

&lt;p&gt;Quick test:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-sI&lt;/span&gt; http://example.com/page | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-i&lt;/span&gt; &lt;span class="nt"&gt;-E&lt;/span&gt; &lt;span class="s2"&gt;"^(HTTP|location)"&lt;/span&gt;
curl &lt;span class="nt"&gt;-sI&lt;/span&gt; https://www.example.com/page | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-i&lt;/span&gt; &lt;span class="nt"&gt;-E&lt;/span&gt; &lt;span class="s2"&gt;"^(HTTP|location)"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Every non-preferred variant should return &lt;code&gt;301&lt;/code&gt; with a &lt;code&gt;Location&lt;/code&gt; pointing to the one true URL.&lt;/p&gt;

&lt;h3&gt;
  
  
  Bug 2: Every page canonicalised to the homepage
&lt;/h3&gt;

&lt;p&gt;I've seen this from theme settings and from SEO plugins misconfigured during migration. Result: Google drops nearly every page as "alternate." Your site doesn't look penalised — it just looks like it has one page.&lt;/p&gt;

&lt;p&gt;Check: view source on three random inner pages. If the canonical is the homepage on all of them, stop reading this and fix that first.&lt;/p&gt;

&lt;h3&gt;
  
  
  Bug 3: Canonical pointing to a noindexed, redirected, or 404 URL
&lt;/h3&gt;

&lt;p&gt;Conflicting signals. You're saying "the real version is over there," and "over there" is a dead end. Google usually ignores the canonical and picks something itself — often not what you want.&lt;/p&gt;

&lt;p&gt;Rule: &lt;strong&gt;a canonical target must return 200, be indexable, and self-canonicalise.&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Bug 4: Paginated archives canonicalised to page 1
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;/blog/page/2/&lt;/code&gt; canonicalising to &lt;code&gt;/blog/&lt;/code&gt; tells Google page 2's posts are "the same" as page 1's. Older posts lose a discovery path. Let paginated pages self-canonicalise.&lt;/p&gt;

&lt;h3&gt;
  
  
  Bug 5: Relative or malformed canonicals
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;&amp;lt;link rel="canonical" href="/page"&amp;gt;&lt;/code&gt; works in theory but breaks easily behind proxies, staging domains, or CDNs. I've seen staging URLs (&lt;code&gt;staging.example.com&lt;/code&gt;) leak into production canonicals after a deploy. Use absolute URLs, and grep your build for your staging hostname.&lt;/p&gt;

&lt;h3&gt;
  
  
  Bug 6: Canonical in the body or set twice
&lt;/h3&gt;

&lt;p&gt;Two canonical tags (one from the theme, one from a plugin) with different values = Google may ignore both. Also, a canonical injected by JavaScript after render is weaker than one in the raw HTML.&lt;/p&gt;

&lt;h2&gt;
  
  
  A 10-minute canonical check for a small site
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Search Console → Pages report.&lt;/strong&gt; Look at "Alternate page with proper canonical tag" and "Duplicate, Google chose different canonical than user." Open examples. Are any of them pages you actually want ranked?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;URL Inspection&lt;/strong&gt; on your 5 most important pages. Compare "User-declared canonical" with "Google-selected canonical." If they differ, your signals disagree.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;View raw source&lt;/strong&gt; (not DevTools Elements) and search for &lt;code&gt;canonical&lt;/code&gt;. Exactly one, absolute URL, in &lt;code&gt;&amp;lt;head&amp;gt;&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sitemap check.&lt;/strong&gt; Every URL in your sitemap should be its own canonical. Sitemaps listing non-canonical URLs send mixed signals.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Internal links.&lt;/strong&gt; Link to the canonical version everywhere — no &lt;code&gt;?ref=&lt;/code&gt;, no non-slash variants in your nav.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Redirect check&lt;/strong&gt; for protocol/host/slash variants with &lt;code&gt;curl -I&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  How I decide: canonical, redirect, or noindex?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Situation&lt;/th&gt;
&lt;th&gt;Use&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Duplicate must stay accessible (params, filters, syndication)&lt;/td&gt;
&lt;td&gt;Canonical&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Duplicate shouldn't exist (old URL, http, www variant)&lt;/td&gt;
&lt;td&gt;301 redirect&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Page is unique but shouldn't be in search (thank-you, internal search)&lt;/td&gt;
&lt;td&gt;&lt;code&gt;noindex&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Page is thin / empty / broken&lt;/td&gt;
&lt;td&gt;Fix or remove it — not a canonical&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;That last row is the big one. Canonicals are often used to "hide" thin pages behind a better one. Google tends to see through that, and you're left with a confusing index.&lt;/p&gt;

&lt;h2&gt;
  
  
  Takeaway
&lt;/h2&gt;

&lt;p&gt;On a small site, canonicals should be boring: every indexable page self-canonicalises, parameter variants point to the clean URL, and everything else is handled by redirects or &lt;code&gt;noindex&lt;/code&gt;. If your canonicals are doing anything clever, that's usually a sign there's a bug underneath.&lt;/p&gt;

&lt;p&gt;I wrote a fuller walkthrough of &lt;a href="https://riichimirza.com/how-to-fix-duplicate-content-with-canonical-tags/" rel="noopener noreferrer"&gt;how to fix duplicate content with canonical tags&lt;/a&gt; on my site — this DEV post is the small-site triage version I use in freelancing audits.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;— Riichi Mirza&lt;/em&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>webdev</category>
      <category>beginners</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
