Video Is Not the Main Content of the Page: Should You Fix It?

If Search Console says “Video is not the main content of the page,” first decide whether the page is meant for watching a video. A supporting video on a useful article or service page may not need a fix. If the page is genuinely a video destination, investigate its layout, rendered player and indexing requirements instead of adding more schema blindly.

There is an important wording update: Google’s current Video indexing report documentation uses “Video isn’t on a watch page.” Older screenshots and tutorials use the main-content phrase. This guide explains the distinction and gives WordPress site owners a decision process for both descriptions.

What the message means—and what it does not

Google introduced the older wording in its December 4, 2023 video-search announcement. The announcement distinguished pages primarily built for watching from pages where a video supports other content. It was not an instruction to turn every blog post into a video landing page.

A video-indexing reason concerns the video’s eligibility in that page context. Do not treat it as proof that the text page has disappeared from ordinary Search, that the website has a manual penalty, or that all embedded videos are broken.

Keep three outcomes separate in your notes: page indexing, video indexing and actual search performance. They answer different questions and can change independently.

The methodology here is an editorial diagnostic framework based on current Google documentation reviewed on October 16, 2026. Worked examples are hypothetical. They illustrate decisions rather than measured ranking improvements or tests carried out on a client website.

Start with the visitor’s job

Ask: if the video were removed, would the page still fulfil its main promise? A written troubleshooting guide might remain useful without its optional walkthrough. A page titled as a recorded workshop would fail its promise if the recording disappeared.

Then ask whether visitors are likely to choose the result specifically to watch. This is a content and business decision before it is a technical one.

Page purpose	Likely decision	Reason
Written guide with a short explanatory embed	Keep the article’s structure	The supporting video does not need to become the page’s main job
Service page with a client introduction clip	Protect the service enquiry journey	A large player should not displace essential service information merely to change a report
Recorded tutorial with a transcript	Review as a watch-page candidate	Watching the specific recording is the primary visitor task
Gallery of unrelated equally prominent clips	Evaluate individual watch destinations only if useful	A list of videos is different from a page devoted to one video
Background decorative video	Do not pursue video indexing for its own sake	Decoration is not a meaningful standalone search destination

“No action” can therefore be a documented, sensible resolution. The aim is useful search visibility and a good destination—not making every report row green.

Step 1: record the exact affected URL and reason

Open the Video indexing report and select an example URL. Record the reason currently displayed, the page you expect Google to use and the video you believe should be detected. Do not start with a sitewide theme change based on one old screenshot.

The current report documentation describes the watch-page reason and other distinct causes, such as an undetermined player position or missing thumbnail. It also explains that this is not an inventory of every unique video on the website.

Use the reason as a hypothesis. A page can have more than one issue, and the most visible label is not necessarily a complete repair specification. Capture a baseline before editing so you can tell which change addressed which condition.

Step 2: separate page-indexing problems from video problems

Inspect the containing page in Search Console. If the page itself is not indexed, resolve the relevant page-level problem before expecting its video to be indexed from that destination.

Check the final URL, canonical intent, response status and whether important content is accessible. Do not add a video sitemap to compensate for a page accidentally marked noindex. A sitemap does not override a contradictory page configuration.

For WordPress, inspect what the active SEO plugin actually outputs rather than assuming a dashboard toggle is the complete story. A theme, CDN or separate plugin may add another directive. Use the broader technical SEO audit checklist when the problem extends beyond video.

Keep development environments private. Never remove staging protection just to make a live test resemble production; perform search diagnostics on the intended public destination after an approved deployment.

Step 3: inspect what loads before interaction

Open the page on mobile and desktop, then use available URL Inspection live-test output to compare what Google can render. A normal browser visit and a crawler test are different pieces of evidence; neither should be represented as the other.

Look for a player that exists in the rendered page, not just a screenshot that becomes a player after clicking. Check whether a slider hides it, a tab keeps it inactive or a huge introductory block pushes it far away from the page’s actual promise.

Record concrete observations: “The recording is inside the third closed accordion” is actionable. “Google does not like the design” is not.

Do not bypass legally required consent controls or weaken privacy choices to load an embed earlier. If consent handling limits discovery, review compliant technical alternatives with the responsible developer and privacy adviser. Search eligibility is not permission to disregard visitor choices.

Step 4: improve a genuine watch page

If watching one specific video is the intended task, make that obvious to a visitor. Use a clear video-specific heading, a prominent usable player and supporting context that helps someone decide whether to watch.

Google’s video best-practice guide describes a dedicated watch page and other eligibility conditions, including an indexed destination and a stable accessible thumbnail. It also makes clear that indexing the page alone does not guarantee indexing its video.

A practical watch-page brief could contain:

• A title describing the actual recording, not a generic “Videos” heading.
• The primary player near the start of the main content.
• A concise summary of what the recording demonstrates.
• A helpful transcript or notes, accurate to the recording.
• Relevant follow-up resources rather than a wall of unrelated embeds.
• Mobile controls that are visible and usable without obstructive overlays.

There is no universal word-count or player-height trick in this brief. Do not delete a useful transcript to manipulate a text-to-video ratio. Design around the intended experience and test the rendered result.

Step 5: align metadata with the actual video

Inventory the video information produced by the theme, SEO plugin, embed plugin and any custom markup. Conflicting descriptions or thumbnails can make diagnosis harder. Choose an implementation owner instead of allowing multiple tools to generate competing definitions.

Google’s VideoObject documentation specifies the markup and required properties for relevant features. Use the real recording’s name, thumbnail and upload information; distinguish the embedded player URL from the underlying media-file URL.

Do not invent a direct MP4 address for a hosted player. Do not mark the article’s cartoon featured image as the video’s thumbnail unless it genuinely represents that recording and is appropriate for the implementation.

Validate the resulting markup and compare it with the visible page. Passing a structured-data test is useful evidence about markup, not proof that Google has accepted the page as a watch destination or will show a rich result.

Worked example: one topic, two legitimate destinations

Imagine a Pakistani freelancer publishing a detailed written WordPress tutorial. Halfway down is a short screen-recorded demonstration. The article answers the question with text, diagrams and steps. The freelancer sees a video-indexing issue and considers moving the clip above everything else.

The better first decision is to preserve the article’s primary job. If people want written instructions, the clip can remain supplementary. Record that video indexing is not the objective for that URL and continue checking the article’s ordinary search performance.

Now imagine the same freelancer also has a substantial recorded workshop that visitors specifically want to watch. A dedicated recording page may be useful: it introduces that workshop, presents the player prominently and includes a transcript and relevant resources.

These pages need different promises. The written guide should not be duplicated word for word on the watch page simply to create a second search entry. Link between them where helpful, and give each destination a clear role. Creating a watch page is justified by the visitor task, not by the existence of an error label.

A compact diagnostic log for agencies

Use one row per investigated destination. This turns a vague report into an accountable decision.

Field	What to write
Primary intent	Read instructions, evaluate a service or watch a named recording
Observed reason	Exact current report wording, not a paraphrased client complaint
Page evidence	Indexing status, expected canonical and response observations
Player evidence	Visible on load, rendered location and interaction dependencies
Decision	Accept supplementary status, repair watch page or investigate another reason
Follow-up	Change owner, deployment date and next review

Capture only the information needed for the diagnosis. Redact client accounts, private video URLs and personal data before sharing screenshots in a report.

What to do after making a change

Retest the deployed page and confirm that the intended correction actually appears publicly. Compare mobile rendering, the player, thumbnail and metadata with the baseline. Then use the relevant Search Console validation or indexing tools when available for that issue.

A live test reflects the current fetch, while stored reports may reflect earlier processing. Do not repeatedly redesign the page during the waiting period or promise a fixed indexing date. Review the evidence before choosing a second intervention.

Measure the outcome appropriate to the decision. For a watch page, look for video-related visibility alongside relevant engagement. For a supporting article, focus on whether people find and use the written answer. For a service page, protect the enquiry journey.

Common mistakes that waste time

• Adding schema only: accurate markup cannot change an article’s underlying purpose.
• Making every video huge: prominence without a useful watch experience can damage the page.
• Copying the same transcript everywhere: duplication does not create a distinct visitor task.
• Confusing host performance with website performance: YouTube results do not automatically establish indexing on your own domain.
• Promising eligibility as a result: meeting technical conditions is not a ranking or rich-result guarantee.

For channel optimisation beyond this particular diagnosis, see the existing broader video SEO guide. Keep that wider strategy separate from repairing an individual report reason.

Frequently asked questions

Will this message stop my article ranking?

It does not, by itself, establish a text-indexing failure. Inspect the page and its ordinary performance separately rather than inferring the whole story from a video report.

Should I remove the video?

Not merely to reduce report noise. Keep a supporting clip if it helps readers. Remove it only for a genuine editorial, usability, rights or performance reason.

Do I need to host the video myself?

No universal self-hosting requirement follows from this message. The relevant issue is the destination’s purpose and eligibility, not simply who stores the recording.

Should I create a watch page for every short clip?

No. Create one when there is a useful standalone watching task. A tiny decorative or repetitive clip rarely justifies another near-empty URL.

The right fix starts with the right objective

Decide whether visitors came to read, evaluate or watch. Accept supplementary-video status where appropriate; investigate rendering and eligibility where a real watch destination is failing. A clear decision backed by evidence is more valuable than redesigning a useful page to satisfy an isolated report label.