SEO记录

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://yourdomain.com/sitemap_index.xml

<!-- 每个可索引页面使用自己的规范网址；由 SEO 插件自动生成时不要重复添加 -->
<link rel="canonical" href="https://yourdomain.com/exact-url-of-this-page/" />

<!-- 分页第 2 页指向第 2 页自身，不要指向第 1 页 -->
<link rel="canonical" href="https://yourdomain.com/blog/page/2/" />

# Check for redirect chains (each hop wastes crawl budget):
curl -IL https://yourdomain.com/old-page/

# Ideal: 301 directly to final destination
# Bad: 301 → 302 → 200 (chain loses PageRank)

# In Nginx — direct 301, no chains:
server {
    return 301 https://www.yourdomain.com$request_uri;
}

# Force www → non-www (pick one, stick to it):
if ($host = "www.yourdomain.com") {
    return 301 https://yourdomain.com$request_uri;
}

<!-- Sitemap index (Yoast generates this at /sitemap_index.xml) -->
<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap><loc>https://yourdomain.com/post-sitemap.xml</loc></sitemap>
  <sitemap><loc>https://yourdomain.com/page-sitemap.xml</loc></sitemap>
</sitemapindex>

<!-- What to EXCLUDE from sitemap:
- Tag pages (/tag/*)
- Author pages (/author/*)
- Search results pages
- Paginated URLs beyond page 2
- Any page with noindex meta tag
- Any page with thin content (<300 words) -->

# Pages that waste crawl budget (block in robots.txt or noindex):
- Faceted navigation: /products/?color=red&size=M
- Session/query parameters: /page/?session_id=abc123
- Pagination beyond page 3: /blog/page/47/
- Print versions: /page/?print=1
- Internal search: /?s=query
- Duplicate content: /category/ overlapping /tag/

# How to check crawl budget in GSC:
# Search Console → Settings → Crawl Stats
# If "Response codes" shows many 404s or redirects = wasted budget

# Noindex tag (best for thin pages you can't delete):
<meta name="robots" content="noindex, follow">

<!-- For sites in multiple languages — prevents duplicate content penalty -->
<!-- On English page: -->
<link rel="alternate" hreflang="en" href="https://example.com/page/" />
<link rel="alternate" hreflang="zh-Hans" href="https://example.com/zh/page/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/page/" />

<!-- Rules:
1. Every page must reference ALL language versions including itself
2. The relationship must be reciprocal (zh page must point back to en)
3. x-default = fallback for users in no-match country/language
4. Use full absolute URLs, not relative paths -->

# Google site: operator (approximate):
site:yourdomain.com

# Exact URL check in Google:
site:yourdomain.com/your-page/

# GSC URL Inspection Tool:
# 1. Go to Search Console
# 2. Paste URL in top search bar
# 3. "URL is on Google" = indexed
# "URL is not on Google" + "Discovered - currently not indexed"
#   = Google knows it exists but hasn't crawled it yet
# "Crawled - currently not indexed"
#   = Google crawled it but decided not to index it (thin content / duplicate / quality issue)

# Crawl depth rule: every important page must be reachable
# in 3 clicks from the homepage.
# Orphan pages (zero internal links) may never get indexed.

# Find orphan pages: Screaming Frog → Reports → Orphan Pages
# (requires uploading your sitemap)

# Priority internal link targets — add to sidebar/footer/body:
# 1. Your highest-traffic pages (boost them with more links)
# 2. Pages stuck at position 6-15 (internal links help them climb)
# 3. New posts (homepage/recent posts widget)

# Anchor text rule:
# 50% exact match keyword: "best WordPress caching plugin"
# 30% partial match: "caching plugins for WordPress"
# 20% generic: "read more", "this article"

# Good URL structure:
https://yourdomain.com/wordpress-seo-guide/          ✓ flat, keyword-rich
https://yourdomain.com/tools/seo-checker/            ✓ one level deep

# Bad URL structure:
https://yourdomain.com/2024/08/05/category/my-post/  ✗ date + category = deep
https://yourdomain.com/?p=1234                        ✗ parameter-based

# WordPress permalink setting: Settings → Permalinks → Post name
# This gives you: yourdomain.com/post-slug/

# URL slug rules:
# - Lowercase only
# - Hyphens between words (not underscores)
# - Remove stop words: a, the, and, in, of, for
# - Max 4-5 words
# - Must contain primary keyword

# Nginx config — security headers that also help SEO trust signals:
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
add_header X-Frame-Options "SAMEORIGIN" always;
add_header X-Content-Type-Options "nosniff" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;

# Force HTTPS redirect (required for HTTPS ranking signal):
server {
    listen 80;
    server_name yourdomain.com www.yourdomain.com;
    return 301 https://yourdomain.com$request_uri;
}

# Test your headers:
# https://securityheaders.com → aim for A+
# https://observatory.mozilla.org → aim for A+

# Formula: [Primary Keyword] — [Benefit or Qualifier] | [Brand]
# OR: [Primary Keyword]: [Number] [Proven Methods] for [Audience]

# Examples:
"WordPress Speed Optimization — 15 Fixes Under 30 Minutes | OrdinaryManTrying"
"Best VPN for China: 7 That Still Work in 2025"
"How to Fix WordPress 500 Error (5 Causes + Exact Solutions)"

# Rules:
# - Max 60 characters (580px pixel width)
# - Primary keyword in first 3 words
# - Every title must be UNIQUE across the whole site
# - Include year for "best X" and "top X" posts (Google rewards freshness)
# - Numbers and brackets increase CTR: [], (), numbers, "How to"
# - Never write clickbait — your bounce rate will tank rankings

# Formula: [Acknowledge the problem] + [What you cover] + [CTA or differentiator]
# Max 155 characters. Not a ranking factor — but affects CTR.

# Good examples:
"WordPress site running slow? This guide covers 15 speed fixes — server, database,
images, and caching. Most take under 5 minutes. No developer needed."

"Stuck at position 6? This free SEO audit checklist covers 30 technical and
on-page checks. Find what Google is penalizing you for in 20 minutes."

# Rules:
# - Include primary keyword (Google bolds matching terms in results)
# - Write for humans, not robots
# - One specific benefit or proof point
# - Avoid passive voice: "Learn how X can be done" → "Fix X in 10 minutes"
# - Never duplicate meta descriptions across pages

# Correct H-tag structure for a 2000-word article:

H1: Best WordPress Caching Plugins (2025) — ONE H1 per page, matches title tag
  H2: Why Caching Matters for WordPress Speed
  H2: Top 7 WordPress Caching Plugins Compared
    H3: 1. WP Rocket — Best Overall
    H3: 2. W3 Total Cache — Best Free Option
    H3: 3. LiteSpeed Cache — Best for LiteSpeed Servers
  H2: How to Set Up WordPress Caching (Step-by-Step)
    H3: Step 1: Install Your Chosen Plugin
    H3: Step 2: Configure Browser Cache
    H3: Step 3: Enable Gzip Compression
  H2: Frequently Asked Questions

# Rules:
# - ONE H1 per page — non-negotiable
# - H2s should naturally include secondary keywords
# - H3s answer the H2's question in detail
# - H2/H3 text should be questions or keyword phrases people actually search
# - Do NOT skip levels: H1 → H3 (skipping H2) is wrong

# Where primary keyword MUST appear:
✓ Title tag — ideally first 3 words
✓ H1 — exactly or near-match
✓ First 100 words of the article
✓ At least one H2
✓ Meta description
✓ URL slug
✓ Image alt text (at least one)
✓ Last 100 words of the article

# Where secondary / LSI keywords should appear:
✓ Other H2/H3 headings
✓ Body text naturally — no stuffing
✓ Image file names: best-wordpress-caching-plugin.jpg

# Keyword density: NOT a metric to optimize for
# Target: mention primary keyword every ~200-300 words naturally
# If you are counting % density, you are doing it wrong

# File name (rename before uploading):
best-wordpress-caching-plugin-comparison.jpg  ✓
IMG_20240801_134522.jpg                        ✗

# Alt text formula: describe what is in the image + include keyword where natural
<img src="wp-rocket-settings.jpg"
     alt="WP Rocket plugin settings page showing cache preloading options"
     width="1200" height="675" loading="lazy">

# What NOT to do in alt text:
alt="wordpress caching plugin wordpress speed wordpress cache"  ✗ keyword stuffing
alt=""  ✗ missing alt (accessibility + SEO fail)
alt="image"  ✗ useless

# Image optimization checklist:
# ✓ WebP format (not JPEG/PNG — 25-35% smaller same quality)
# ✓ Max width 1200px for blog images
# ✓ Under 100KB per image
# ✓ loading="lazy" on all images below the fold
# ✓ Specify width and height (prevents CLS layout shift)

# Rule 1: Link from high-authority pages to new pages
# Your homepage and top-traffic pages pass the most link equity.
# Add a "Related Posts" or "Further Reading" section manually.

# Rule 2: Use descriptive anchor text (not "click here")
# Bad:  <a href="/caching-guide">click here</a>
# Good: <a href="/caching-guide">WordPress caching guide</a>

# Rule 3: The 3-click rule — every page reachable in 3 clicks
# Use site:yourdomain.com in Google to find orphan pages

# Rule 4: Number of internal links per page
# Homepage: link to all main category/pillar pages
# Blog posts: 3-7 internal links per 1500-word post

# Rule 5: Fix broken internal links immediately
# Broken internal links waste crawl budget and lose PageRank
# Tool: Broken Link Checker WP plugin, or Screaming Frog

# Featured snippets (Position 0) appear above regular results.
# Types: paragraph, list, table, video

# How to get a paragraph snippet:
# 1. Target a "what is" or "how to" question
# 2. Answer it in 40-60 words immediately after the question heading
# 3. Use simple declarative sentences

# Example structure:
## What Is WordPress Caching?
[40-60 word definition here — direct, no fluff]
[Longer explanation continues after the snippet-optimized paragraph]

# How to get a list snippet:
# Use H2 or H3 for each list item
# Keep each item brief (under 10 words)
# Aim for 5-8 items

# How to get a table snippet:
# Use an actual HTML <table> element
# First column = items, subsequent columns = attributes
# Table must be visible in the page (not hidden behind JS)

# Triggers for a content update (check each post annually):
# ✓ Ranking has dropped 3+ positions over 3 months
# ✓ CTR dropped without position change (title/desc needs update)
# ✓ "Year" in title is outdated (2023 article in 2025)
# ✓ Screenshots / UI screenshots are outdated
# ✓ Statistics cited are older than 2 years
# ✓ New competitor pages are outranking you

# What to update:
# - Update date (but ONLY if you actually updated content)
# - Add new sections covering angles competitors cover that you don't
# - Update statistics and screenshots
# - Add FAQ section from current People Also Ask results
# - Remove outdated plugins/tools and replace with current ones
# - Add new internal links to newer posts

# WordPress: update the "Last modified" date in Yoast/RankMath
# Changing publish date can reset social share counts — bad idea

# LCP measures how fast the biggest visible element loads.
# Usually the hero image or H1 text.

# Step 1: Find your LCP element
# PageSpeed Insights → scroll to "Opportunities"
# DevTools → Performance tab → run recording → find LCP marker

# Step 2: Fix slow LCP image:
# In WordPress theme header.php or functions.php:
add_filter('wp_get_attachment_image_attributes', function($attr, $attachment) {
    if (is_front_page() && /* is hero image */) {
        $attr['loading'] = 'eager';
        $attr['fetchpriority'] = 'high';
    }
    return $attr;
}, 10, 2);

# In HTML directly:
<img src="hero.jpg" fetchpriority="high" loading="eager" alt="...">

# Step 3: Preconnect to external resources:
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="dns-prefetch" href="https://fonts.gstatic.com">

# Step 4: Use a CDN — moves static assets closer to users

# CLS = elements jumping around as the page loads.
# Most common causes:

# 1. Images without dimensions — FIX: always specify width/height
<img src="photo.jpg" width="1200" height="675" alt="...">

# 2. Ads without reserved space — FIX in CSS:
.ad-container { min-height: 250px; }

# 3. Web fonts causing FOUT — FIX: preload fonts
<link rel="preload" as="font" href="/fonts/myfont.woff2"
      type="font/woff2" crossorigin>

# 4. CSS font-display: swap causes text reflow — use optional instead
@font-face {
    font-display: optional; /* renders only if font loads fast enough */
}

# 5. Dynamically injected content above existing content
# Never inject banners/popups above the fold after page load

# INP replaced FID in March 2024. Measures responsiveness to ALL interactions.
# Main cause: heavy JavaScript blocking the main thread.

# Diagnosis in DevTools:
# Performance tab → record a click interaction
# Look for "Long Tasks" (red blocks > 50ms) on the main thread

# WordPress-specific fixes:
# 1. Defer non-critical JavaScript:
<script src="script.js" defer></script>
<script src="tracking.js" async></script>

# 2. WP Rocket settings:
# → File Optimization → Delay JavaScript Execution → Enable
# → Exclude: jquery.min.js, /wp-includes/js/

# 3. Remove unused plugins — every plugin adds JS
# Test with Query Monitor plugin to see which plugin adds what JS

# 4. Break up long tasks with setTimeout:
# If you have custom JS loops, yield to main thread periodically

# Nginx: enable browser caching and compression
# Add to your server {} block:

gzip on;
gzip_vary on;
gzip_min_length 1000;
gzip_proxied any;
gzip_comp_level 6;
gzip_types text/plain text/css text/xml application/json
           application/javascript application/xml+rss
           application/atom+xml image/svg+xml;

# Browser caching:
location ~* .(jpg|jpeg|png|gif|ico|css|js|webp|woff2)$ {
    expires 1y;
    add_header Cache-Control "public, immutable";
}

# Cache-Control for HTML pages (short TTL):
location ~* .html$ {
    add_header Cache-Control "public, max-age=3600";
}

# In order of impact — do these first:

# 1. Switch to a fast host (biggest single factor)
#    LiteSpeed server + NVMe SSD + PHP 8.2 = baseline advantage

# 2. Install a caching plugin
#    WP Rocket (paid) or W3 Total Cache (free)
#    Enable: page cache + browser cache + database cache

# 3. Image optimization
#    ShortPixel or Imagify → auto WebP conversion on upload
#    Lazy load all images below the fold

# 4. Use a CDN
#    Cloudflare free → significant improvement for global audiences
#    BunnyCDN ($1/mo) → best performance/price for static assets

# 5. Optimize database
#    WP-CLI: wp db optimize
#    Delete post revisions: wp post delete $(wp post list --post_type=revision --format=ids)

# 6. Minimize plugins
#    Every active plugin adds PHP execution + often JS/CSS
#    Target: under 15 active plugins

# Step 1: Generate seed keywords
# Think like your target reader: what problem are they trying to solve?
# Seed: "wordpress speed", "caching plugin", "slow wordpress"

# Step 2: Expand seeds with tools
# → Google Autocomplete (type keyword + space + each letter A-Z)
# → People Also Ask box results
# → Related Searches at bottom of SERP
# → AnswerThePublic.com
# → Ahrefs / Semrush free keyword tools

# Step 3: Filter by INTENT (most important step)
# Informational: "how to speed up wordpress" → blog post
# Commercial: "best wordpress caching plugin" → comparison post
# Transactional: "buy wp rocket" → product page
# Navigational: "wp rocket login" → don't target

# Step 4: Filter by DIFFICULTY for your site's authority
# New site (DR 0-20): KD < 20, volume 100-1000/mo
# Growing site (DR 20-40): KD < 40, volume 500-5000/mo
# Established site (DR 40+): can target KD up to 60

# Step 5: Group into topic clusters
# 1 pillar page per main topic + 5-10 supporting posts

# The 4 intents — mismatching = you will never rank

# INFORMATIONAL — user wants to learn
# Signals: "how to", "what is", "why does", "guide", "tutorial"
# Content type: blog post, guide, listicle
# Example: "how to fix wordpress white screen of death"

# COMMERCIAL INVESTIGATION — user comparing options
# Signals: "best", "vs", "review", "top", "alternatives to"
# Content type: comparison post, review, roundup
# Example: "wp rocket vs w3 total cache"

# TRANSACTIONAL — user ready to buy/act
# Signals: "buy", "pricing", "discount", "coupon", "download"
# Content type: sales/product page, pricing page
# Example: "wp rocket coupon code"

# NAVIGATIONAL — user wants specific site
# Signals: brand name + feature
# Do NOT target: "wp rocket login", "netflix sign in"
# These searchers are going to another site, not yours

# How to assess if you can rank for a keyword:

# Step 1: Google the keyword
# Count how many results on page 1 are from:
# - Wikipedia, Forbes, NYT, major brands → very hard
# - Mid-size blogs with 100-500 posts → possible
# - Small personal blogs → winnable

# Step 2: Check Domain Rating / Authority of top 10
# Use Ahrefs free Keyword Generator or Moz
# Your DR should be within 20-30 points of the median top-10 DR

# Step 3: Check backlinks to #1 result
# Ahrefs free checker: https://ahrefs.com/backlink-checker
# If top result has 500+ backlinks → too hard for a new site
# Under 50 backlinks → attainable

# Step 4: Check content quality gap
# Can you write a genuinely better, more comprehensive page?
# "Better" = more current, more specific, covers more subtopics
# If you can't say WHY yours would be better → don't compete yet

# Long-tail = 4+ words, lower volume, higher conversion, lower competition

# Generate long-tails from a head term:
# Head: "wordpress caching"
# Long-tails:
# "best wordpress caching plugin for woocommerce"
# "how to set up wordpress caching on shared hosting"
# "wordpress caching plugin not working with cloudflare"
# "is wordpress caching worth it for small sites"

# Tactics to find them:
# 1. Google Autocomplete — type partial query
# 2. "People Also Ask" box — goldmine for long-tails
# 3. GSC → Performance → Queries (filter: position > 15)
#    These are keywords you ALMOST rank for — target them
# 4. Keyword Sheeter — generates 1000s from one seed
# 5. Answer queries in FAQ sections to target voice search long-tails

# Target 1 primary keyword + 3-5 secondary long-tails per article

# Find keywords competitors rank for that you do not

# Method 1: Ahrefs Content Gap (free limited version)
# Site Explorer → enter your domain → Content Gap
# Enter 2-3 competitor domains
# Filters: top 10 positions, volume > 100

# Method 2: Manual GSC + Semrush
# 1. List your top 10 competitors (Google your main keywords)
# 2. Enter each into Semrush free Organic Research
# 3. Look at their "Top Pages" — find posts you don't have
# 4. These are content gaps to fill

# Method 3: "vs" and "alternative" keywords
# If competitor is BigPlugin:
# "bigplugin vs [your niche alternative]"
# "bigplugin alternatives"
# "is bigplugin worth it"
# Write comparison pages — searchers at buying stage

# Priority: focus on competitor pages ranking #4-#10
# They are beatable. #1-#3 requires significant link investment.

# CONTENT BRIEF — paste into Google Docs before writing

TARGET KEYWORD: [primary keyword here]
SECONDARY KEYWORDS: [3-5 related keywords]
SEARCH INTENT: [Informational / Commercial / Transactional]
TARGET WORD COUNT: [average of top 3 results + 20%]

TITLE TAG: [60 chars max, keyword first]
META DESCRIPTION: [155 chars max]
URL SLUG: [keyword-only, max 5 words]

HEADINGS OUTLINE:
H1: [matches title]
H2: [covers main subtopic 1 — keyword variation]
  H3: [specific point]
  H3: [specific point]
H2: [covers main subtopic 2]
H2: [FAQ section — 3-5 questions from People Also Ask]

COMPETITOR GAPS TO COVER:
- [what competitor 1 covers that we should too]
- [angle they miss that we can own]

INTERNAL LINKS TO ADD:
- Link FROM this post to: [related post 1], [related post 2]
- Link TO this post from: [high-traffic existing post]

# Topic cluster = 1 pillar page + 5-10 cluster pages, all interlinked

# Example cluster: WordPress Security
# ┌─ PILLAR: "WordPress Security — The Complete Guide 2025"
# │   (2500+ words, broad overview of the whole topic)
# │
# ├── CLUSTER: "WordPress Security Plugins Compared"
# ├── CLUSTER: "How to Set Up Two-Factor Authentication in WordPress"
# ├── CLUSTER: "WordPress File Permissions Guide (chmod values)"
# ├── CLUSTER: "How to Find and Remove WordPress Malware"
# ├── CLUSTER: "WordPress Brute Force Attack Protection"
# └── CLUSTER: "WordPress Security Hardening Checklist"

# Linking rules:
# - Every cluster post links to the pillar page
# - Pillar page links to all cluster posts
# - Cluster posts link to 2-3 other cluster posts

# Why it works: Google sees a site that covers a topic
# comprehensively and treats it as an authority on that topic.

# Stop chasing word count. Target comprehensiveness.

# How to set correct length:
# 1. Google your target keyword
# 2. Count words in top 3 results (use Word Counter browser extension)
# 3. Your target = average of top 3 + 20%
# BUT: only add content that adds value, not filler

# Content that adds real depth:
# ✓ Original data or examples from your own experience
# ✓ Step-by-step screenshots for how-to content
# ✓ A comparison table competitors don't have
# ✓ A FAQ section from current PAA questions
# ✓ Common mistakes section
# ✓ Tool recommendations with real reasons

# Content that is pure filler (hurts dwell time):
# ✗ Restating the same point 3 different ways
# ✗ Lengthy preamble before getting to the answer
# ✗ Padding with obvious context the reader already knows
# ✗ "In conclusion, we learned that..."

# Run this check on your top 20 posts every 6 months:

# Rankings check (GSC → Performance → Pages):
[ ] Post dropped 3+ positions in last 90 days
[ ] CTR is below 3% for position 1-3 (title/meta needs work)
[ ] Impressions dropped (Google reduced indexing coverage)

# Content quality check:
[ ] Year in title is outdated
[ ] Screenshots show outdated UI
[ ] Statistics cited are 2+ years old
[ ] Tools/plugins mentioned are discontinued or superseded
[ ] Missing topics that competitors added since your original post
[ ] New People Also Ask questions not covered

# Technical check:
[ ] Internal links to outdated posts
[ ] Broken outbound links (use Broken Link Checker)
[ ] Images not in WebP format

# Action trigger: 2+ checks = update the post
# Update minimum: add 300+ words, fix all outdates, update modified date

# Google's position: AI content is fine IF it is helpful and accurate.
# Google penalizes: mass-produced AI content with no added value.

# The safe workflow:
# 1. Research the topic yourself first — know what needs to be covered
# 2. Use AI to draft structure and fill in known facts
# 3. Add: your own experience, original examples, screenshots
# 4. Add: specific data/statistics with sources
# 5. Edit for your voice — remove "it's worth noting", "delve into", etc.
# 6. Fact-check every claim — AI hallucinations are an E-E-A-T destroyer

# AI red flag phrases to delete:
# "It's worth noting that", "Notably", "In conclusion", "Overall",
# "Delve into", "Leverage", "Embark on", "Tapestry of",
# "In today's fast-paced world", "In the realm of"

# What makes AI content safe:
# ✓ First-person experience ("When I tested this...")
# ✓ Specific examples from your niche
# ✓ Accurate statistics with real citations
# ✓ Screenshots and original media

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title Here — Max 110 Characters",
  "description": "Your meta description here — 150 characters.",
  "image": "https://yourdomain.com/images/featured-image.jpg",
  "author": {
    "@type": "Person",
    "name": "Your Name",
    "url": "https://yourdomain.com/about/"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Your Site Name",
    "logo": {
      "@type": "ImageObject",
      "url": "https://yourdomain.com/logo.png"
    }
  },
  "datePublished": "2025-01-15",
  "dateModified": "2025-08-01",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://yourdomain.com/your-article-slug/"
  }
}
</script>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How do I speed up my WordPress site?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The fastest way to speed up WordPress is to install a caching plugin (WP Rocket or W3 Total Cache), optimize your images to WebP format, and use a CDN like Cloudflare. These three steps alone can improve your PageSpeed score by 30-50 points."
      }
    },
    {
      "@type": "Question",
      "name": "What is a good PageSpeed score for WordPress?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Aim for 90+ on mobile and 95+ on desktop in Google PageSpeed Insights. Anything above 75 on mobile is acceptable. Below 50 on mobile will negatively impact your Core Web Vitals rankings."
      }
    }
  ]
}
</script>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Install a WordPress Caching Plugin",
  "description": "Step-by-step guide to installing and configuring a WordPress caching plugin.",
  "totalTime": "PT10M",
  "estimatedCost": { "@type": "MonetaryAmount", "currency": "USD", "value": "0" },
  "step": [
    {
      "@type": "HowToStep",
      "name": "Go to Plugins",
      "text": "In your WordPress dashboard, navigate to Plugins → Add New.",
      "image": "https://yourdomain.com/images/step1.jpg",
      "url": "https://yourdomain.com/how-to-install-caching/#step-1"
    },
    {
      "@type": "HowToStep",
      "name": "Search for the Plugin",
      "text": "Type W3 Total Cache in the search box and press Enter.",
      "image": "https://yourdomain.com/images/step2.jpg",
      "url": "https://yourdomain.com/how-to-install-caching/#step-2"
    }
  ]
}
</script>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://yourdomain.com/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "WordPress Guides",
      "item": "https://yourdomain.com/wordpress/"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "WordPress Caching Guide",
      "item": "https://yourdomain.com/wordpress/caching-guide/"
    }
  ]
}
</script>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebApplication",
  "name": "WordPress Speed Test Tool",
  "description": "Free tool to test and diagnose WordPress loading speed with actionable recommendations.",
  "url": "https://yourdomain.com/tools/speed-test/",
  "applicationCategory": "UtilitiesApplication",
  "operatingSystem": "Any",
  "offers": {
    "@type": "Offer",
    "price": "0",
    "priceCurrency": "USD"
  },
  "featureList": [
    "One-click speed analysis",
    "Core Web Vitals diagnosis",
    "Actionable recommendations"
  ]
}
</script>

Subject: Guest post idea for [their site]: "[your specific article title]"

Hi [First Name],

I've been reading [their site] for a while — your post on [specific article]
really helped me [specific outcome]. That's the kind of practical angle I want
to contribute.

I'd like to write: "[Proposed Article Title]"

Here's why it fits your readers:
• [Specific reader problem it solves]
• [Data point or angle they haven't covered]
• [Why you are qualified to write this]

A quick sample of my writing: [link to your best existing post]

Happy to send an outline first if useful.

[Your name]

---
Rules for this email:
- Subject line: specific article title, not "guest post inquiry"
- Reference ONE specific article of theirs — prove you read it
- Propose a specific title with a clear angle
- Keep it under 150 words
- Never attach anything to first contact

# HARO (now Connectively) — journalists email you queries,
# you respond with expertise, they quote you with a link.
# Free. Works best for DR 40+ links from major publications.

# Response template:
Subject: RE: [Query subject line] — Source: [Your name, credential]

BRIEF CREDENTIAL: [Your name] — [1-line why you are qualified]
E.g.: "John Smith — WordPress developer, 8 years, 200+ sites built"

ANSWER TO QUERY:
[Direct answer in 100-200 words. Specific, not generic.
Include a data point, example, or original insight.
Journalists pick responses that give them a quotable sentence.]

OPTIONAL ADD: [One additional tip or angle they didn't ask about]

CONTACT: [name] | [website] | [email] | [social proof if relevant]

---
Tips:
- Respond within 2 hours of receiving the query (first-come advantage)
- Be specific and quotable — "it depends" answers never get used
- Subscribe to relevant categories only: tech / business / marketing

# Step 1: Find a competitor in your niche with lots of content
# Step 2: Run their site through Ahrefs free backlink checker
#         or Check My Links Chrome extension on their resource pages

# Step 3: Find broken outbound links on popular resource pages
# Search: [your topic] inurl:resources OR inurl:links
# Example: "wordpress tutorials inurl:resources"
# Use Check My Links extension to find all 404s on the page

# Step 4: Find the original content that was at the broken URL
# Use Wayback Machine: https://web.archive.org

# Step 5: Create better content that replaces the dead link

# Step 6: Email the webmaster:
Subject: Broken link on your [page name] page

Hi [name],
I was reading your [page title] page and noticed the link to
"[anchor text]" is returning a 404 ([broken URL]).

I recently published a guide on the same topic that might be a
good replacement: [your URL]

Either way, thought you'd want to know about the broken link.

[Your name]

# Find linkable content → make it better → contact linkers

# Step 1: Find linkable content in your niche
# Ahrefs Content Explorer: search [your keyword]
# Filter: referring domains > 20, published 1-3 years ago
# Find posts with many links but that are outdated

# Step 2: Create the "skyscraper" version — genuinely better by:
# - More current (fresher stats, updated screenshots)
# - More comprehensive (cover subtopics it missed)
# - Better UX (comparison table, downloadable checklist)
# - Original data (run a survey, cite your own tests)

# Step 3: Find who links to the original
# Ahrefs → enter original URL → Backlinks
# Export the list of linking domains

# Step 4: Outreach email:
Subject: Updated version of [topic] for [their site name]

Hi [name],
I noticed you linked to [original article] in your post on [their article].
That piece hasn't been updated since [year] — a lot has changed.

I just published a fully updated version: [your URL]
It covers [2-3 specific improvements you made].

Thought it might be a useful resource for your readers.

[Your name]

# Your About page is a major E-E-A-T signal. It must include:

# ✓ Real name (not "The Editorial Team")
# ✓ Professional photo
# ✓ Specific credentials relevant to the site topic
#   Bad: "I love blogging and sharing tips"
#   Good: "8 years managing WordPress sites for 200+ clients"
# ✓ Publications or mentions on other sites (with links)
# ✓ Social proof: LinkedIn, Twitter/X, GitHub — public profiles
# ✓ Contact information (real email or form, not just a contact page link)
# ✓ Physical address or at minimum country (trust signal for local)

# For YMYL sites (finance, health, legal):
# ✓ Professional certifications
# ✓ Named expert reviewers with credentials
# ✓ Disclosure policy
# ✓ Medical/legal/financial disclaimer

# Add author bio to every post:
# → In WordPress: Users → Edit Profile → Biographical Info
# → Yoast SEO: adds author structured data from this field

# Add these to your site — each is a concrete trust signal:

# EXPERIENCE signals:
[ ] First-person language: "When I tested...", "In my experience..."
[ ] Original screenshots and photos (not stock)
[ ] Case studies from your own work
[ ] "Last tested: [date]" on review posts

# EXPERTISE signals:
[ ] Author bio on every post with credentials
[ ] Outbound links to authoritative sources (research, official docs)
[ ] Correct use of technical terminology
[ ] No factual errors (fact-check everything)

# AUTHORITATIVENESS signals:
[ ] Editorial links from other sites in your niche
[ ] Guest posts on recognized sites
[ ] Mentions in industry roundups
[ ] Social profiles matching the author name

# TRUSTWORTHINESS signals:
[ ] Privacy Policy page (required for GDPR + trust)
[ ] Terms of Service page
[ ] Disclosure/affiliate disclaimer (FTC required)
[ ] HTTPS certificate (A+ on SSL Labs)
[ ] Contact information visible

# Run this on the first Monday of every month:

# 1. Check Index Coverage (5 min)
# Coverage → Valid with Warnings + Excluded
# Investigate any URLs in "Crawled - currently not indexed"
# Fix or noindex these pages

# 2. Find Position 4-15 Quick Wins (5 min)
# Performance → Queries
# Filter: Position > 3, Position < 16
# Sort by Impressions (highest first)
# These pages are "almost ranking" — small improvements can jump them

# 3. Find Low-CTR High-Impression Pages (5 min)
# Performance → Pages
# Sort by Impressions
# Find pages with CTR below 2% → rewrite title + meta description

# 4. Check Core Web Vitals (3 min)
# Experience → Core Web Vitals
# Any URLs marked "Poor" → fix immediately (affects rankings)

# 5. Check for Manual Actions (1 min)
# Security & Manual Actions → Manual Actions
# "No issues detected" = good. Any issues = fix before anything else

# The most valuable GSC query for finding quick wins:

# In GSC → Performance → Queries:
# Date range: last 3 months
# Filter: Position > 3 AND Position < 16
# Sort by: Impressions (descending)
# Export to spreadsheet

# For each page in this list, do:
# 1. Open the page
# 2. Check the title tag — does it match intent + include keyword?
# 3. Check first paragraph — does it answer the query immediately?
# 4. Check: does the page cover subtopics the top-3 results cover?
# 5. Add 1-2 internal links from higher-authority pages

# The math: page at position 8 with 500 impressions/month
# Gets roughly 3% CTR = 15 clicks
# Move to position 3: 10% CTR = 50 clicks
# Same page, 3x traffic. No new content needed.

# Cannibalization = two pages competing for the same keyword
# Google cannot decide which to rank → both rank lower

# How to find it in GSC:
# Performance → Queries
# Search for your target keyword
# Click the keyword → see which pages appear
# If 2+ pages appear for the same query = cannibalization

# How to fix:
# Option A: Merge — combine both pages into one stronger page (301 redirect the weaker one)
# Option B: Differentiate — change one page to target a different intent
# Option C: Noindex — if one is clearly lower quality, noindex it
# Option D: Canonicalize — if one is a subset, point canonical to the main page

# Prevention:
# Before writing a new post, search your own site:
# site:yourdomain.com "target keyword"
# If a relevant page already exists → update it instead of creating a new one

# Run monthly — each item is pass/fail

CRAWLING & INDEXING:
[ ] robots.txt accessible and correct (yourdomain.com/robots.txt)
[ ] Sitemap submitted to GSC and no errors
[ ] No pages in GSC "Excluded" that should be indexed
[ ] HTTP → HTTPS redirect working (test with curl -IL http://yourdomain.com)
[ ] www/non-www consistency (pick one, 301 the other)
[ ] No redirect chains (test with redirect-checker.org)

ON-PAGE:
[ ] Every post has unique title tag (60 chars max)
[ ] Every post has unique meta description (155 chars max)
[ ] No duplicate H1s across the site
[ ] All images have alt text
[ ] No broken internal links

PERFORMANCE:
[ ] Google PageSpeed mobile score > 75
[ ] Core Web Vitals: all "Good" in GSC
[ ] No render-blocking resources flagged in PageSpeed

SECURITY:
[ ] SSL certificate valid (check expiry: openssl s_client -connect yourdomain.com:443)
[ ] Security headers grade: A or better (securityheaders.com)
[ ] WordPress + plugins + theme all up to date

# Quarterly content audit — categorize every post as:

# KEEP (no action needed):
# - Ranking in top 5 for target keyword
# - Traffic stable or growing month-over-month
# - Content still accurate and current

# IMPROVE (update within 30 days):
# - Ranking position 4-20 (quick win opportunity)
# - Title/meta description older than 1 year on time-sensitive topics
# - Screenshots outdated (more than 6 months for UI-heavy tutorials)
# - Missing FAQ section (People Also Ask results changed)

# CONSOLIDATE (merge with another post):
# - Two posts targeting same keyword
# - Posts under 500 words covering same subtopic
# - Old roundup post superseded by a newer comprehensive guide

# DELETE (with 301 redirect to best alternative):
# - Zero organic traffic for 12+ months
# - Outdated content that cannot be updated (old product reviews)
# - Thin content with no strategic value