Research and grow with Search Console

Use Search Growth as the research workspace

Search Growth brings site-scoped Search Console evidence, plans, optimization work, indexing checks, and internal-link operations into one workspace. Use it when the question begins with what is happening in search, which page needs attention, or what action should enter the content workflow next.

This is BlogFactory’s equivalent of a research-to-action surface: the useful output is not another dashboard. It is a traceable decision that can become a new article brief, a revision, an indexing investigation, or an internal-link task.

Choose the right tab

Overview

Read site totals, trends, opportunities, and data provenance before choosing an action

Plan

Turn evidence into a bounded growth plan with explicit review status

Optimize

Prepare page-level content improvements without overwriting a newer draft

Analytics

Compare page and query performance within a declared date window

Indexing

Inspect URL and sitemap state when the question is about discoverability

Internal Links

Review site-scoped link suggestions and apply only approved changes

Read Overview and Analytics

Overview and Analytics use property-level, date-grouped Search Console data with the source, range, fetch time, completeness boundary, scope, and cache provenance attached. The default research window is 28 complete reporting days.

Start with clicks, impressions, CTR, position, pages, and queries, then narrow the comparison. Reporting is delayed and bounded; label preliminary dates and do not turn a sparse row into a confident recommendation.

Trend or opportunity

Use complete-day Overview and Analytics evidence

Page/query comparison

Keep the filter and date window visible in the decision

One URL

Move to Indexing and use URL inspection

Sitemap question

Read the connected sitemap state instead of inferring from totals

Build a Growth Plan

1. Choose the active site and verify that Search Console data is recent enough for the question.
2. Review the evidence and proposed opportunities rather than accepting every generated item.
3. Keep the plan bounded to a specific page, query, content gap, or technical check.
4. Set the review decision and move only an approved item into Create Content or Optimize.
5. Revisit the declared observation window before judging the outcome.

Prepare an optimization

Optimize is for an existing page or BlogFactory draft that needs a controlled change. Read the current content and Search Console evidence together, define the page-level objective, and keep the recommendation attached to its source window.

If the target is a saved draft, revision protection still applies. Reread the current version and use expected_updated_at so a background job or teammate’s newer work is never overwritten.

Diagnose indexing

Use Indexing when the question is why a particular URL is or is not discoverable. URL inspection and sitemap state provide URL-level evidence; a property-wide coverage total does not explain an individual page.

Record the inspected URL, observed state, and check time. If the provider has not returned enough evidence, keep the result inconclusive instead of inventing a cause.

Review internal links

Internal Links keeps link discovery and review inside the active site. Inspect the proposed source page, destination page, anchor context, and current revision before applying a suggestion.

The accepted change enters the same draft and review workflow as other edits. BlogFactory does not silently update a live CMS page.

1. Review the source and destination context.
2. Reject irrelevant, repetitive, or misleading anchors.
3. Apply the approved suggestion to the current BlogFactory draft.
4. Review the rendered draft before CMS delivery.

Move research into action

A reviewed opportunity can open Create Content with the target query and recommended direction, or open Optimize for an existing page. From there, the normal generation, revision, review, and CMS draft-only boundaries apply.