fig. beginning/Guides/SEO Optimisation/Content Details

Data tracking and continuous optimisation:

Make SEO a closed loop (see it, do it, check it)

SEO is most likely to fall into two extremes:

  • One-time configuration only: Install the plugin, submit the sitemap, post the article, and then “wait”.
  • Anxiety about staring at data every dayThe first time the rankings fall, then change, change the title today, tomorrow look at the CTR, do not understand to continue to search for tutorials.

The real way to stabilise growth is to turn SEO into a line ofReusable closed loop：

Monitor health → spot opportunities → set priorities → make small changes → validate results → precipitate templates → next time faster

This article is for this closed loop, which you must be able to do after reading it:

  • You know which metrics to track (few and critical)
  • You can run a fixed pace on a “weekly/monthly/quarterly” basis.
  • Can you make a quick judgement: yesProblems with indexingYesClick-through rates are downorContent mismatch
  • You know how to accept the changes after you've made them (instead of going by feel)
  • The more you can sink your effective methods into a template, the easier it gets to do it

1. Closing the loop: tracking is not about “looking at data”, it's about “making decisions”.”

Break SEO Continuous Optimisation down into 6 steps and you'll never mess up:

  1. Health monitoring (haemostasis): Are there any anomalies in the crawling/indexing/errors?
  2. Opportunity scanning (growth): Which pages are “almost better”?
  3. prioritisation: High impact, low cost, low risk first.
  4. small change: Change only one type of variable at a time (title/first screen/internal links/content depth).
  5. Validation and Review: Look at trends, look at controls, look at time windows, not 48 hours.
  6. Precipitation template: Solidify effective practices into title templates, structure templates, FAQ templates, and internal linking rules.

If you only do 1-3 steps, you will always be stuck in the “read a lot of reports but don't know what to do”.
If you only do 4-6 steps and don't monitor them, it's “too late to fix it if you don't know it's happening”.

2. Tool framework: each tool answers only one question (don't use tools as targets)

Need you to remember:What questions each tool is responsible for answering. No need to learn all the features first.

2.1 Search Console: The Hub for Crawling, Indexing, and Search Performance

It answers four main things:

  • Have you been arrested?(Crawl error, redirect failure, server unavailable)
  • Has it been indexed?(why not indexed) -Page indexing report The reasons for “not indexed” will be listed in categories such as blocked by robots.txt, duplicate pages, etc.
  • How did the search perform?(clicks/displays/CTR/average ranking) -Performance report It's these four core indicators.
  • How many crawlers are coming and how well does the site hold up?——Crawl Stats report Used to view crawl requests, responses, availability issues, etc.

You can think of Search Console as the “check-up centre” for SEO.

2.2 Analytics (e.g. GA4): the hub of user behaviour and business results

Search Console tells you “what's happening on the search side” and Analytics tells you “what's happening after the user comes in”.

There are only two pieces you need most:

  • Engagement: GA4“s engagement rate / bounce rate is centred around "engaged sessions”Defined.
  • Key events: GA4 allows important events to be labelled as key event, used to measure behaviours that are important to the business.

You can think of Analytics as the “close and quality check” of SEO.

2.3 Operational monitoring (optional but very valuable): downtime, certificates, 5xx, speed fluctuations

It answers a simple question:

  • Are you “unaware” that the site is slowing down/hanging/reporting errors?

SEO is afraid of “site quality problems continue for a week you did not find”, and when you find, crawling and indexing has been affected.

2.4 Ranking/competitor monitoring: just look at trends, no emotional switches

It's suitable for use:

  • Look for “Rank 8-20” sprints.
  • Observe whether the core theme is rising/falling overall

It's not suitable for use:

  • Stare at a single word every day for mood swings
  • The page will be changed if we drop two of you today.

3. Indicator system: 4 tiers of indicators to bring all data together

Layer the metrics so you don't get overwhelmed with reports.

Layer 1: Healthiness (can you catch, can you index)

You have to watch it every week:

  • crawl error (computing): 404, 5xx, redirection errors
  • index coverageWhat is not indexed and why?Page indexing report (A table of reasons “why not indexed” will be included)
  • Site Map Status: Success/Failure, Exception URL
  • Crawl statistics: crawl counts, response status, availability issues (Crawl Stats report）

The goal of this layer: don't let “technical issues” choke off growth.

Layer 2: Search performance (has it been seen, clicked)

You have to look at it every month:

  • strike (on the keyboard)
  • showcase
  • CTR
  • Average ranking (just look at the trend)

The four indicators are Search Console The heart of performance reporting.

The goal of this layer: to find the “opportunity page” (close is better).

Layer 3: Page quality (is there any value for people coming in)

You have to look at it every month:

  • Participation (Engagement rate (/bounce rate) - GA4 is clear on the definition and relationship between engagement rate, bounce rate.
  • Key actions (key events) - Marking important events as key events is used to measure business value.
  • Entry page quality: which pages bring inquiries/registrations/orders, and which only have “fake traffic”.”

The goal of this layer: to avoid “traffic going up but business not changing”.

Layer 4: Experience and template health (slow or not, jumpy or not, interaction stuck or not)

This layer doesn't require you to tweak parameters every day, but you need to be able to spot “template-level problems”.

Core Web metricsis the most commonly used set of languages: LCP, INP, CLS and suggested thresholds (e.g. LCP 2.5s, INP 200ms, CLS < 0.1).

The goal of this layer: don't let experiential issues drag down overall performance.

4. Rhythm: weekly bleeding, monthly growth, quarterly upgrades (SEO into a “fixed habit”)

4.1 Weekly: abnormal checks (haemostasis)

You can catch big accidents early by doing just 20-30 minutes a week.

Weekly list of exceptions (check in order)

  1. Whether index coverage changes abnormally
    • Page indexing report will tell you the category of reasons for “not indexed” (e.g. robots.txt blocks, duplicate pages).
  2. Does the crawl error grow
    • 404, 5xx, redirection failure
  3. soft 404 presence/increase
    • soft 404 is “page not shown to exist but returns 200”, which Search Console flags in the index report.Officials also explainedThe common causes and manifestations are discussed.
  4. Is the site map reporting errors
  5. Whether the crawl statistics are abnormal (a sudden drop in the number of crawls/longer response times)
    • Crawl Stats report Used to view crawl history, request volume, response with availability issues.

Weekly output：

  • A “list of this week's anomalies” (3-10 items), with each item: phenomenon → suspected cause → next step.

You will find: SEO real disaster, often not “competitors are stronger”, but “your site is broken you do not know”.

4.2 Monthly: Inventory of opportunities (growth)

Doing a monthly “opportunity scan” is the most consistent source of growth.

Opportunity type 1: CTR opportunity (lowest risk, fastest payoff)

Judgement rules：

  • High display but significantly low CTR (same type of query/same type of page comparison)

Usual causes：

  • The title/summary is not clear and the reader doesn't know what to expect when they click on it
  • SERPs appear new or strong and your results look “unattractive”.”

Prioritisation of actions (from low to high risk)

  1. Change Title: to express more clearly “what problem is solved + for whom + what you offer”.”
  2. Change Description: Explain in two sentences “what you will get + key highlights”.”
  3. Change the first screen: make the first screen understandable in 10 seconds (interlinked with your “on-page optimisation checklist”)
  4. Only rewrite the structure if you are sure that the content does not match the intent

Receiving and Inspection Criteria(at least one of which is satisfied)

  • CTR up
  • Click to rise
  • and there was no significant deterioration in engagement due to title induction (as seen with GA4)

Benefits of this type of optimisation: it doesn't require changing a lot of content and doesn't trigger indexing risks.

Opportunity type 2: Ranking 8-20 (best value “sprint zone”)

Judgement rules：

  • It's close to the first page, but it's not breaking through
  • Usually “a piece of content is missing,” “the structure is not clear enough,” and “there are not enough internal links.”

List of common gaps (by frequency of occurrence)

  • Lack of examples: only concepts, no examples
  • Lack of contrast: readers want to compare A/B, you only talk about A
  • Missing step: no executable process
  • Missing FAQ: didn't answer the reader's next question
  • Lack of internal links: the site does not vote for this page as a “key page”.

Action Priority

  1. Filling in the “missing piece” (example/comparison/steps/FAQ)
  2. Enhanced internal linking: pointing to this page from a topic page/related content page (anchor text description is clear)
  3. Updating outdated information (especially tutorials/tools/screenshots of interfaces)
  4. Then consider more complex structured data extensions (don't just pile on schema)

Receiving and Inspection Criteria

  • Average ranking from 8-20 into top 10 (or close)
  • or a significant rise in clicks/displays

Opportunity type 3: Decline of old content (best value for money)

Judgement rules

  • Good performance over the past 3-12 months, recent decline
  • Content may be out of date, competitors have updated, page structure no longer matches

Action (immobilisation highly recommended)

  • Updating of key paragraphs (addition of new information, deletion of outdated content)
  • Replace expired screenshots
  • Addition of “last updated” information (to increase credibility)
  • Merge duplicates: two similar ones into a stronger one (and processed with a 301)

Receiving and Inspection Criteria

  • Show Recovery, Click Recovery
  • Related queries become more numerous (wider coverage)

4.3 Per quarter: structural upgrading (making growth more stable)

There doesn't need to be a lot of quarterly moves, but with each one, the site will be more resistant to fluctuations:

  • Make thematic pages/aggregation pages to link content on the same topic into a system
  • Reconstructing the internal chain: upward/parallel/downward three-way structure
  • Cleaning up the contents of the sheet: merge/rewrite/delete
  • Template-level optimisation: make all article pages/product pages automatically more standardised (reduce human costs)

5. Examination tree: what to look for first when you see an anomaly (don't make changes so you can fix it quickly)

Here's the most “life-saving” part: you can avoid “fixing the mess” by checking the problems in the order you encountered them.

5.1 Scenario A: Sudden drop in indexing/indexing

Prioritisation (deadliest to most common)

  1. Whether noindex or rule blocking
    • Page indexing report flags reasons for “not indexed”, such as robots.txt blocking, duplicate pages, etc.
    • robots.txt official guideThere are also clear warnings against using robots.txt as a way of hiding pages; URLs blocked by robots.txt may still appear in search results, but instructions are missing; if you want to block from appearing in search results, you should use something like noindex.
  2. Are there a lot of 5xx/availability issues
    • HTTP 5xx slows down crawling and may lead to eventual removal from the index; 4xx excludes indexing;official documentAlso explains that network/DNS errors are treated as 5xx.
  3. Is the site map abnormal
    • Submitting a sitemap is just a hint, it doesn't guarantee a crawl, but a sitemap error could cost you a “structural hint”.
  4. Whether the revamp resulted in a URL change or redirection error

Principles of treatment: Restore crawlability and indexability first, then talk about content and rankings.

5.2 Scenario B: No change in rankings, but clicks are down

This is usually a CTR issue or SERP change.

sequencing of investigations

  1. Whether there are new styles of SERPs/new strong opponents (your results are squeezed out)
  2. Is the title/abstract unclear and unattractive (CTR down)
  3. Whether the page is slow or unstable (users don't want to click on it, or click on it and back off)
  4. Is there a mismatch in the intent of the page (user clicks in and finds it's not what they want)

deal with: Prioritise CTR and first screen optimisation (low risk).

5.3 Scenario C: You change the content but see no results

The most common here is “you think you've changed it, but Google hasn't caught it yet / the change is too big to attribute”.

sequencing of investigations

  1. Whether or not it was actually captured
    • You can use the URL Inspection request to crawl a single URL, but an official reminder: requests have quotas, and multiple requests won't get it crawled any faster.
  2. Is the change too great (can't tell which factor is effective)
  3. Are you changing the wrong direction (content doesn't fulfil the intent, more changes won't help)
  4. Is it affected by cache links (browser cache/CDN/source cache lets you see older versions)

deal with: Each subsequent change is a “change log + small step iteration + acceptance window” (see Section 7).

6. Clarify the “action library”: what exactly to change for each opportunity (in order of risk)

6.1 CTR Optimisation of the action library (from safest to most efficient)

Action 1: Title Clarity (highest priority)

  • Write the headline as “Readers know what to expect at a glance.”
  • Don't rely on stacking keywords, rely on clear value

Action 2: Description becomes “Page Summary”.”

  • In two sentences: what problem do you solve + what key content do you provide?
  • Let readers click in with an expectation that they won't click by mistake, causing them to bounce.

Action 3: First screen promises consistency

  • The first screen of the first screen gives the conclusion/roadmap/checklist directly
  • Avoid a first screen full of “backstory.”

Action 4: Make the page more credible in the SERPs

  • Add update time, author information (if appropriate)
  • Add a clear structure (table of contents, list of points)

an inventory of received goods: CTR up + clicks up + engagement not significantly worse (GA4).

6.2 8-20 Sprint Movement Bank (“Filling Gaps” is most effective)

Fill them one by one against the list of gaps below:

  • default step → Add “Roadmap/Step List”
  • lack of comparison → Add “Comparing Dimensions and Recommended Scenarios”
  • lack of examples → 1 example for each key concept
  • Missing FAQ → add 8-12 questions to cover the reader's next question
  • missing links → Vote for it from a strong page on the same topic (inline pointing)

an inventory of received goods: Ranking in the top 10 or a significant increase in clicks.

6.3 Updating the action library with old content (“updating is not rewriting”, it's patching up what needs to be patched up the most)

You only do three things per update:

  1. Updating outdated information (tool interface, rule changes, old screenshots)
  2. Fill in the “gap paragraphs” (add a new section on key issues)
  3. Enhancement of internal linking (to get new content into the thematic system)

an inventory of received goods: Show & Click Recovery, covering queries becomes more.

7. Validation and attribution: making every change you make “valid”

The most painful thing about SEO is not the lack of growth, but the growth you don't know why; the decline you don't know where it is caused. There is only one solution:Standardised recording and acceptance。

7.1 Record of changes (minimum usable version)

You will only remember 6 items for each change:

  • URL
  • Date of change
  • What was changed (title/summary/first screen/FAQ/internal links/updates)
  • Scope of change (single page or template)
  • Expected Impact (CTR Increase / Ranking Increase / Conversion Increase)
  • Acceptance window (2-4 weeks) and acceptance indicators

As soon as you start to remember, SEO immediately turns from a “metaphysics” into a “project”.

7.2 Iterating in small steps (changing one type of variable at a time)

Don't take a breath:

  • change title + change body + change structure + change URL + change schema
    You never know what works that way.

Order of recommendation (low risk to high risk):

  1. Title/Description
  2. top screen structure
  3. FAQ/Gap Filler
  4. internal chain
  5. Template-level changes
  6. URL changes (most prudent, involving migration and redirection)

7.3 Control group (to let you know if it was you who made the changes)

The control group was simple:

  • Looking for the same type of page (same theme/same template) but you didn't move it
  • Compare its trend over the same time window

If the control group drops together as well, it probably is:

  • Industry fluctuations, SERP changes, seasonal variations
    Instead, you changed it for the worse.

7.4 Correct Expectations for “Request Crawl/Accelerated Inclusion”

When you release an important update, you can grab individual URLs with a URL Inspection request, but it's officially and explicitly warned:

  • With submission quota
  • Multiple requests for the same URL won't make crawling faster

So the correct approach is:

  • Use it as a tool to “trigger a check”.
  • Don't use it as an “accelerator”

8) Technical issues dedicated to troubleshooting: 404, soft 404, 5xx, robots.txt, migration

8.1 404 vs soft 404: Why soft 404s are more annoying

  • 404: true does not exist, return 404
  • soft 404: the page tells the user “gone/empty”, but the server returns 200
    official explanation soft 404: Returns 200 but the page content indicates that it does not exist, could be an empty page, empty internal search results, missing JS, etc.

soft 404 Common Trigger Scenarios

  • Site search results are empty but returned 200
  • Products taken down showing “no content” but still 200
  • Missing JS resource causes blank page
  • CMS template error outputting empty shell page

Restoration principles

  • Returns 404/410 if it really doesn't exist
  • Take down products either do a 301 to the most relevant alternative page or a 410 (depending on the business)
  • Empty search pages should not normally be indexed (and avoid being included in site maps)

8.2 Impact of 4xx/5xx on crawling and indexing (must be taken seriously)

Official Description:

  • 4xx excludes URLs from indexing
  • 5xx slows down crawling and may lead to eventual removal from the index
  • Network/DNS errorwill be treated as 5xx

So one of the most important moves you'll make each week：
Keep an eye on 5xx and redirection errors to take out site stability issues first.

8.3 The division of labour between robots.txt and noindex (don't get it wrong)

The main use of robots.txt is to manage crawler traffic;Officials also warnedDon't use robots.txt as a way to hide pages, and point out that URLs blocked by robots.txt may still appear in search results.

Practical conclusions

  • Think “don't catch” → robots.txt
  • Think “Don't appear in search results” → noindex/permissions/remove
  • Mix rules carefully to avoid conflicts (validate on a small scale before rolling out)

8.4 Revision migration: the most feared is not to drop a little ranking, but “mapping did not do”.”

Migration (URL changes, domain name changes)There is official documentation, emphasising the need to prepare new sites, prepare URL mapping, and minimise negative impacts.

Migration of minimum standards (master page level)

  • Export the list of old URLs first
  • Do the old → new mapping table (don't all point to the home page)
  • Post-launch focus on: 404, soft 404, redirect chains, index coverage changes
  • Staged relocation is more stable than “all in one go”

9. Experience and speed: making “experience” measurable with Core Web Vitals

Core Web Metrics (CWV) are a set of metrics that measure real user experience and give suggested thresholds, for example:

  • LCP: within 2.5 seconds if possible
  • INP: Try to stay within 200ms
  • CLS: below 0.1 as far as possible

The Right Use of CWV in Continuous Optimisation

  • You don't have to look at it every day.
  • But when you find: CTR is normal, rankings are normal, clicks are normal, but conversions drop or bounces rise
    → Often times it's the experience/speed that holds it back
  • When you make big theme/plugin/template changes
    → A CWV review is mandatory to avoid “template level accidents”.”

10. Make it SOP: weekly/monthly fixed tasks

10.1 Weekly SOP (haemostasis)

  1. Check for index coverage exceptions (Category of reasons not indexed）
  2. Check for crawl errors (404/5xx/redirect failures)
  3. 查 soft 404 whether or not
  4. Check the site map status (remember:Submitting just prompts）
  5. search and seizeStatistical anomalies(Crawl, response time, availability)

Output: list of exceptions for the week (3-10) + order of handling (5xx, then 404, then others)

10.2 Monthly SOP (growth)

  1. CTR Opportunity: Pick 10 pages → Change Title/Description/First Screen
  2. 8-20 Opportunities: Pick 10 pages → Fill in the gaps + internal link voting
  3. Older content update: pick 5 articles → update outdated information + add key passages
  4. 404/redirect maintenance: clean links, patch mapping
  5. Review: record what actions worked → write up templates (title template, FAQ template, structure template)

Output: list of opportunities for this month (pages 10-30) + completed list + plan for next month

10.3 Quarterly SOP (structural upgrade)

  1. Make 1-3 topic pages/aggregation pages
  2. Refactoring of internal links (up/parallel/down)
  3. Clean up the contents of the book (merge/rewrite/delete)
  4. Template-level experience review (CWV/mobile readability)

Output: quarterly restructuring programme + “templated specifications” (for teams to write in a uniform way)

11. Frequently asked questions

1. Why is the Search Console data not real-time?

This is a normal phenomenon. You have to use the “trend” and “time window” to make a judgement, do not use “today changed tomorrow must rise” to make a judgement.

2. low CTR change title or content first?

Change the title/summary with the first screen first (low risk), then go back and change the content to match the intent if the CTR comes up but engagement gets worse.

3. What if clicks go up but conversions don't?

See if Analytics' key events are dropping or the quality of the entry page is deteriorating.GA4 supports tagging important events as key event to measure business critical behaviours.
It could be that the “headline is attracting the wrong people” and needs to be adjusted to match the promise with the content.

4. Why is the sitemap still not included after submission?

This is because submitting a sitemap is only a hint, not a guarantee of crawling or indexing.
To go back to index coverage reasons, content quality, and site stability troubleshooting.

5. soft 404 What is it? What should I do with it?

soft 404 is a case where 200 is returned but the page indicates that it does not exist or is empty.Search Console Will mark.
Processing: really does not exist on the return 404/410; down to do the relevant 301; empty results page to avoid indexing.

6. I've updated my content, how do I get Google to see it faster?

It is possible to grab a single URL with a URL Inspection request, but there is a quota and multiple requests will not be faster.
The right thing to do: make sure the site is crawlable, internal links are discoverable by crawlers, and the site is stable.

7. When should I do a feature page?

When you find a group of content related to the theme, each other weak internal links, the user needs to “from the beginning to advanced” path, it should be a thematic page, which can improve the understanding of the structure and internal polling efficiency.

8. Does it make sense to look at the rankings every day?

Not so much. It's more effective to do a monthly “rank range opportunity scan” and spend your energy on actions that will drive growth.

9. Will changing the URL affect SEO?

will, so change it only when necessary and do the URL mapping with redirects as per the migration process;Official Migration DocumentationEmphasis was placed on preparing for mapping and reducing negative impacts.

10. My site occasionally 5xx, is it necessary to care?

Yes. 5xx slows down crawling and may lead to eventual removal from the index;Network/DNS errorIt will also be treated as a 5xx.
Stability is the first priority in continuous optimisation.