Mobile-first Indexing and Structured Data: Keep Images, Metadata and Rich-result Signals Consistent

Mobile-first indexing means Google primarily uses the mobile version of your website for crawling, rendering, indexing and ranking. That sounds straightforward until your mobile pages contain different images, truncated metadata, missing schema, weaker internal links or a separate URL structure that changes the meaning of the page.

The risk is not limited to mobile rankings. Inconsistent mobile and desktop signals can create duplicate content SEO issues, weaken rich-result eligibility and make it harder for Google to understand which page should rank for a query. When several URLs also target similar keywords, the problem can develop into keyword cannibalization, with your own pages competing against one another across devices.

This guide explains how mobile-first indexing interacts with structured data, image SEO, metadata, internal linking and search intent. It also shows how to audit the whole system, identify conflicts and build a repeatable workflow with SEO Letters, an AI blog writing and publishing platform for structured, search-focused content.

What Mobile-first Indexing Actually Means for SEO

Mobile-first indexing does not mean Google has a separate mobile index and a separate desktop index. Google generally maintains one index, but it uses the mobile version of a page as the primary source for evaluating content and signals.

That distinction matters. Your desktop page might contain a complete article, detailed product schema and carefully written title tag, while the mobile version shows a shortened or different experience. Google is likely to rely on what it can access from the mobile version.

In practical terms, mobile-first indexing affects:

Main content and supporting copy
Title tags and meta descriptions
Canonical tags
Robots directives
Structured data
Image files and image alt text
Internal links
Navigation paths
Product, review and breadcrumb signals
Page experience and loading behaviour
Embedded media and JavaScript-rendered content

The mobile version does not need to look identical to the desktop version. It does need to communicate the same core information and support the same search intent.

That is the important distinction. A responsive design usually makes consistency easier, but a responsive layout does not automatically guarantee consistent SEO signals.

Mobile-first indexing versus mobile usability

Mobile usability focuses on whether people can use your page comfortably on a smaller screen. Mobile-first indexing focuses on what Google can crawl, render and interpret from that version.

A page can be mobile-friendly but still create indexing problems if:

Important text is hidden from the mobile DOM
Structured data is missing from the mobile HTML
Images use different URLs or lower-quality assets
Internal links disappear on mobile
A mobile subdomain serves a different canonical
The mobile version includes a noindex directive
Lazy-loaded content is unavailable without interaction
Metadata points to a different page or topic

This whole thing is often treated as a design issue. It is really a content architecture issue as well.

Why Structured Data Must Match the Mobile Page

Structured data helps search engines interpret entities, relationships and page types. It can support rich results such as FAQs, breadcrumbs, product listings, review snippets, articles and events, although valid markup never guarantees enhanced visibility.

Google evaluates structured data in the context of the page where it appears. If the mobile version contains incomplete, inaccurate or contradictory markup, your rich-result signals may become unreliable.

For example, imagine a desktop product page that includes:

Product name
Brand
SKU
Price
Availability
Aggregate rating
Review count
High-resolution product images

If the mobile version removes the price, shows a different product name and uses a separate image, Google may see conflicting information. The page could lose eligibility, or the search engine may choose to ignore some properties.

Core structured-data consistency checks

Your mobile and desktop versions should normally align on the following:

Structured-data element	What should remain consistent	Common mobile-first problem
`@type`	The page type, such as Article, Product or FAQPage	Mobile template uses generic WebPage markup
`name` or `headline`	The visible page or product title	Mobile heading is shortened beyond recognition
`description`	The page summary where applicable	Mobile metadata describes a different offer
`image`	Relevant, crawlable images representing the entity	Mobile markup uses a missing or tiny asset
`author`	The same identifiable author or organisation	Author data is removed from mobile content
`datePublished`	Original publication date	Mobile page shows only the updated date
`dateModified`	Genuine update date	Dates change without editorial updates
`offers`	Price, currency and availability	Mobile price is hidden or outdated
`aggregateRating`	Supported, visible rating information	Rating markup remains on desktop only
`mainEntityOfPage`	The correct canonical page	Mobile schema references the desktop URL incorrectly
`breadcrumb`	The same hierarchy and page position	Mobile breadcrumbs are reduced or omitted

The markup must describe content that is available to users on the page. Hiding structured-data-supported information from mobile visitors can create a mismatch even if the JSON-LD itself is technically valid.

Structured data does not repair weak content

Schema is a classification layer. It does not compensate for a thin page, unclear search intent or duplicated content.

If three pages target the same commercial keyword and each includes identical Product or Article schema, the markup does not resolve the underlying keyword cannibalization. You still need to decide which URL serves the primary intent, which pages should be merged, and how the internal linking system should reinforce that decision.

The Relationship Between Mobile-first Indexing and Keyword Cannibalization

Keyword cannibalization occurs when multiple pages on the same website appear to target the same keyword or satisfy the same search intent. It is not simply a case of using the same phrase more than once. Several pages can mention the same keyword without causing a problem if they serve clearly different purposes.

The problem becomes more likely when pages overlap in:

Search intent
Page type
Main topic
Title tags
H1 headings
Anchor text
Structured-data entities
Internal-link destinations
Product or service descriptions

Mobile-first indexing can expose or intensify these conflicts because the mobile page may not match the desktop page’s intended role.

Consider this example:

URL	Desktop focus	Mobile focus	Likely outcome
`/mobile-seo/`	Broad mobile SEO guide	Short summary about page speed	Google sees an unclear topic
`/mobile-first-indexing/`	Indexing and crawling	Generic mobile SEO checklist	Topic boundaries become blurred
`/structured-data-mobile/`	Schema consistency	Product-markup troubleshooting	Internal relevance signals conflict

A desktop user might see a clear content hierarchy. Googlebot Smartphone may encounter shorter headings, missing links and reduced structured data. The mobile version then sends weaker signals about which page is authoritative for which query.

Mobile-specific cannibalization patterns

Watch for these patterns during an audit:

Responsive content truncation
The mobile interface hides sections that distinguish one page from another.
Separate mobile URLs with conflicting canonicals
A desktop URL canonicals to itself, while the mobile URL canonicals to another page or has no canonical.
Mobile templates reusing generic metadata
Several pages receive the same mobile title tag or meta description.
Mobile navigation linking to a different target
Important category links disappear, while a broad commercial page receives all the internal authority.
Structured-data duplication
Multiple pages claim to represent the same product, article or organisation.
AMP or cached variants remaining indexable
Older versions compete with current responsive pages.
Faceted navigation creating near-identical mobile URLs
Filters generate crawlable pages with almost no unique value.

A keyword cannibalization audit needs to compare mobile and desktop output, not just inspect the source code of one version.

Search Intent Mapping Before You Change Templates

Before consolidating pages or rewriting metadata, map the search intent behind each URL. This prevents a common mistake: merging pages that look similar but serve different stages of the buying or research journey.

A useful search intent mapping framework includes:

Intent category	Typical query	Appropriate page type	Primary conversion
Informational	What is mobile-first indexing?	Detailed guide	Read, subscribe or explore
Commercial investigation	Best mobile SEO tools	Comparison or category page	Trial or shortlist
Transactional	SEO content automation software	Product or service page	Sign-up
Navigational	SEO Letters app	Brand landing page	Visit the platform
Troubleshooting	Why is my mobile page not indexed?	Diagnostic guide	Audit or service enquiry

Your keyword clustering strategy should group terms that express the same underlying need, not merely terms that share a word.

For example, these keywords may belong to one informational cluster:

Mobile-first indexing explained
How Google indexes mobile sites
Mobile-first indexing SEO
Mobile version not indexed
Googlebot Smartphone crawling

They could support one authoritative guide, with distinct subheadings covering each variation. Creating a separate page for every phrase would increase the risk of thin content and internal linking conflicts.

A practical intent-mapping process

Export the URL set
Include indexed pages, recently published pages, mobile subdomains, parameter URLs and important templates.
Collect query data
Use Google Search Console, a rank tracker and analytics data where available.
Group by intent
Classify queries as informational, commercial, transactional or navigational.
Compare page types
Note whether competing URLs are guides, product pages, category pages, case studies or support documents.
Assign one primary URL
Choose the page that best satisfies the main intent and has the strongest evidence of relevance.
Define secondary roles
Supporting pages should answer narrower questions and link clearly to the primary page.
Align mobile templates
Make sure the mobile page preserves the distinctions identified in the mapping exercise.

SEO Letters can help turn this process into a repeatable publishing workflow. Its keyword research, difficulty ratings and topical authority clustering features are designed to move from a keyword list to a structured content plan rather than producing disconnected articles.

Keeping Images Consistent Across Mobile and Desktop

Images are easy to overlook in mobile-first migrations. Developers often change image URLs, formats, dimensions or loading rules to improve performance. Some changes are sensible. Others remove useful image signals or prevent Google from discovering the primary asset.

Google recommends that important images are available on the mobile version, use crawlable URLs and appear in supported HTML elements or accessible rendered content.

Image consistency checklist

Check that mobile pages preserve:

The primary image used in Article, Product or Recipe schema
Descriptive file names where practical
Relevant alt text
Image captions where they add context
Stable image URLs
Appropriate width and height attributes
Image sitemap references
Open Graph and social preview images
High enough resolution for image search
Lazy-loaded assets that become available without user interaction

A common error is using a desktop image in JSON-LD while displaying a different mobile image. That creates a weak relationship between the markup and the visible content.

Another issue appears when a mobile template swaps the main image for a CSS background image. CSS backgrounds can support design, but they are not always the clearest way to expose an important content image to search engines.

Mobile images and duplicate content SEO issues

Image variants can also create duplicate content SEO issues when image search URLs, resized parameters or CDN versions become indexable.

For example:

/images/guide.jpg
/images/guide-768x432.jpg
/cdn-cgi/image/width=480/guide.jpg
/media/guide?format=webp

These URLs may be perfectly legitimate asset variants, but they should not become competing HTML pages. Review image attachment pages, parameter handling and CDN configuration so search engines do not waste crawl resources on thin versions.

Recommended image workflow

Identify the image that represents the page’s main entity.
Use the same primary image in mobile-visible content and structured data.
Serve responsive sizes through srcset and sizes.
Keep the image URL stable when possible.
Add meaningful alt text that describes the image’s function.
Validate that lazy-loaded images appear in rendered HTML.
Review image sitemap entries and indexation reports.
Test structured-data image properties with Google’s Rich Results Test.

Do not add keywords to alt text simply because the phrase has search volume. Alt text should describe the image accurately for accessibility and context.

Metadata Consistency: Titles, Descriptions and Robots Directives

Metadata is one of the clearest areas where mobile and desktop versions can drift apart. In responsive designs, the HTML is shared, but separate mobile URLs or server-side templates may produce different values.

Your title tag should identify the same page and satisfy the same intent on every indexable version. It does not need to be identical in pixel width across every device, because Google rewrites snippets frequently, but the underlying message should not change.

Metadata audit criteria

Review these fields on both mobile and desktop:

<title>
Meta description
Canonical link
Robots meta tag
hreflang annotations
Open Graph title and description
Twitter card data
Viewport configuration
HTTP X-Robots-Tag
Language and regional signals
Pagination references where relevant

A mobile page with noindex cannot support the same indexing strategy as its desktop equivalent. Similarly, a canonical pointing to a non-equivalent page can create uncertainty, particularly when the target page has different content or intent.

Example of a metadata mismatch

Desktop title:

Mobile-first Indexing Guide: Structured Data and Image SEO

Mobile title:

Mobile SEO Tips | SEO Letters

The second title is broader and brand-heavy. It may cause the mobile page to appear relevant to a different query set. If the mobile URL is indexable, Google could treat it as a separate competing document.

The solution is not always to make every character identical. The goal is semantic equivalence and a clear canonical relationship.

Canonical Tags and Alternate Mobile URLs

Responsive websites are usually easier to manage because one URL serves all devices. Separate mobile URLs, such as m.example.com, require more careful implementation.

For a separate mobile URL setup:

The desktop page should reference the mobile alternate with rel="alternate" where appropriate.
The mobile page should reference the desktop URL as its canonical.
Both versions should contain equivalent primary content.
Redirects should send users to the equivalent mobile or desktop page, not a generic homepage.
Structured data should identify the same entity and canonical page.
Internal links should not create loops or inconsistent destinations.

An incorrect canonical arrangement can create three versions of the same problem:

The desktop page claims authority over the topic.
The mobile page contains the strongest content but canonicalises elsewhere.
Google selects a third URL as canonical because the signals do not agree.

That situation can look like an indexing failure when it is really a consistency failure.

Canonical review questions

Ask:

Does the canonical resolve with a 200 status?
Is it indexable?
Does it satisfy the same search intent?
Does it contain equivalent core content?
Does its structured data reference the correct URL?
Do internal links reinforce the canonical?
Does the sitemap list the preferred version?
Are redirects and hreflang tags aligned?

A canonical is a hint, not an absolute command. Internal links, redirects, content similarity and external references all influence canonical selection.

Internal Linking Conflicts Across Mobile Templates

Internal linking is one of the most useful tools for resolving keyword cannibalization, but mobile templates can quietly weaken it.

Desktop navigation may include links to:

Parent categories
Related guides
Product pages
Comparison content
Supporting definitions
Contact or conversion pages

The mobile version might collapse these links into a menu, remove contextual references or show only a small set of popular pages. This can change the internal authority flow and make topic relationships less obvious.

What internal linking should communicate

Internal links should help Google and users understand:

Which page is the primary resource
Which pages are supporting explanations
How content fits into a topical cluster
What the next sensible action is
Which commercial page is relevant to a problem
Whether two similar URLs have separate purposes

For the topic cluster around mobile-first indexing, a sensible structure might look like this:

Pillar page: Mobile-first indexing explained
Supporting page: Mobile-first indexing and structured data
Supporting page: Mobile page speed and Core Web Vitals
Supporting page: Mobile image SEO
Supporting page: Mobile SEO audit checklist
Commercial page: SEO content automation software

The supporting articles should link back to the pillar with varied, accurate anchor text. The pillar should link to the most relevant supporting pages. Product references should be contextually placed rather than inserted into every paragraph.

SEO Letters supports this kind of structured content production by generating articles with headings, internal-link suggestions, schema and images. You can review the outputs, adjust the anchor strategy and publish directly to WordPress, Shopify or a webhook from the SEO Letters app.

A Complete Mobile-first Indexing and Structured-data Audit

A useful audit combines technical crawling, rendered testing, search data and editorial review. One source rarely shows the full picture.

Step 1: Compare mobile and desktop HTML

Use a crawler with mobile user-agent settings and compare:

Word count
Headings
Main content
Links
Images
Metadata
Canonicals
Robots directives
Structured data blocks
Author and date information

Do not focus only on raw word count. A mobile page can be shorter and still equivalent if it preserves the essential information, but missing sections that answer key queries should be treated as a risk.

Step 2: Test rendered content

Googlebot may process JavaScript differently from a simple source-code crawler. Use URL Inspection in Google Search Console and inspect the rendered HTML.

Check whether:

Main text appears
Product details load
Images are discoverable
Navigation links are present
Schema is injected correctly
Cookie or consent layers block content
Tabs and accordions expose important information

If content appears only after a tap, test whether it is still present in the rendered DOM and accessible without a problematic interaction.

Step 3: Validate structured data

Use:

Google’s Rich Results Test
Schema Markup Validator
Search Console enhancement reports
Manual source and rendered-HTML checks

Record errors, warnings and differences between device versions. A warning may not block eligibility, but it can reveal a data-quality issue, especially when the missing property is important to the page type.

Step 4: Run a keyword cannibalization audit

Build a spreadsheet containing:

Field	Purpose
URL	Identify the page
Mobile URL	Detect alternate versions
Primary keyword	State the intended target
Search intent	Define the user need
Current ranking URL	See which page Google prefers
Organic clicks	Measure traffic contribution
Impressions	Identify visibility
CTR	Assess snippet performance
Conversions	Protect commercial value
Canonical	Check preferred version
Schema type	Compare page classification
Internal links in	Measure authority flow
Recommended action	Merge, retain, redirect or differentiate

Look for cases where two pages rank for the same query at different times, alternate in Search Console or have overlapping titles and headings.

Step 5: Review the keyword clustering strategy

A cluster should have:

One dominant search intent
One primary page
Supporting pages with narrower angles
Clear internal-link relationships
Distinct metadata
Consistent mobile and desktop content

If every keyword receives its own article, you may be manufacturing your own cannibalization problem. A cluster-based model usually produces stronger topical authority and a clearer publishing schedule.

Step 6: Fix conflicts in priority order

A sensible remediation order is:

Indexation blockers
Wrong canonicals and redirects
Missing or contradictory main content
Structured-data errors
Image mismatches
Metadata inconsistencies
Internal linking conflicts
Thin or overlapping articles
Performance and user-experience refinements

This ordering protects the foundations first. There is little value in refining a meta description when the mobile URL is canonicalised to the wrong page.

Case Study: Resolving Three Competing Mobile SEO Articles

Imagine a software company has published three articles:

/mobile-seo-guide/
/mobile-first-indexing/
/mobile-indexing-checklist/

All three mention the keyword “mobile SEO”. On desktop, the first article is comprehensive, the second explains Google’s indexing system and the third offers a checklist. On mobile, however, the template hides the detailed sections and uses the same title prefix for each page.

Search Console shows that the three URLs alternate for “mobile-first indexing”. Organic impressions are spread across them, but none has a stable position.

Audit findings

The guide and checklist share 55% of their visible mobile copy.
The indexing article loses its structured Article markup on mobile.
All three pages link to the same commercial page with identical anchor text.
The checklist title implies a practical task, but its mobile H1 is generic.
The guide contains the strongest external links but does not link to the indexing article.

Recommended action

Keep /mobile-first-indexing/ as the primary explanatory resource.
Retain /mobile-indexing-checklist/ as a focused operational asset.
Rewrite /mobile-seo-guide/ around broader technical SEO and remove duplicated indexing sections.
Restore equivalent Article schema and author information on mobile.
Add contextual links between the three pages.
Change anchor text so each link explains its destination.
Review rankings after four to eight weeks, depending on crawl frequency.

This approach does not rely on deleting pages at random. It uses search intent mapping, content differentiation and signal consistency.

How SEO Letters Supports a Consistent Publishing Workflow

Content quality and technical consistency are connected. When articles are created without a defined cluster, page role or publishing process, duplicate topics and weak internal links become more likely.

SEO Letters is built for teams and publishers that need a complete workflow around content production. It can support:

Keyword research with difficulty ratings
Topical authority clusters
Competitor site-gap analysis
Search-focused article briefs
Structured headings and long-form content
Internal-link recommendations
Schema generation
Image suggestions
Brand voice controls
Product-aware affiliate and ecommerce content
Multi-language generation across 21 languages
Direct publishing to WordPress, Shopify and webhooks
Performance monitoring after publication
Autonomous content campaigns
Content-refresh campaigns for existing pages

The autonomous campaign scheduler is particularly useful when you want a repeatable cadence without creating a new manual brief every week. You define a topic, destination and schedule, then the system can research, write and publish according to the workflow you have configured.

That does not remove the need for editorial review. It gives you a stronger operating system for the work between keyword selection and the live page.

A safe workflow for mobile-first content campaigns

Define the pillar and cluster
Establish the main page, supporting topics and commercial destinations.
Map search intent
Decide whether each page answers a question, compares options, supports a product decision or enables a transaction.
Set content rules
Specify author details, brand terminology, internal links, schema types and image requirements.
Generate the draft
Use SEO Letters to create the article with a clear heading hierarchy and structured sections.
Review mobile equivalence
Check that the mobile template displays all important content and markup.
Validate technical signals
Test canonical tags, robots directives, images, structured data and links.
Publish and monitor
Send the article to your CMS, then track impressions, clicks, rankings and conversions.
Refresh where evidence suggests
Update declining pages rather than automatically creating another article on the same keyword.

The rightbar is the contact path if you need help turning this into a managed SEO content workflow.

Metrics and Benchmarks to Monitor

A technically consistent page should be assessed through outcomes, not just validation tools. Track performance at URL, cluster and device levels.

Core SEO KPIs

Mobile impressions
Mobile clicks
Click-through rate
Average position
Indexed URL count
Rich-result impressions
Rich-result click-through rate
Organic conversions
Assisted conversions
Crawl status
Canonical selected by Google
Core Web Vitals
Internal links to priority pages
Ranking volatility across competing URLs

Useful warning signals

Signal	What it may suggest	Recommended response
Mobile clicks fall while desktop clicks remain stable	Mobile content or metadata changed	Compare rendered versions
Several URLs rank for one query	Possible keyword cannibalization	Run intent and URL-level audit
Rich-result impressions disappear	Schema or visible-content mismatch	Validate markup on mobile
Indexed pages increase after faceted navigation changes	Duplicate or low-value URLs	Review parameters and canonicals
Average position fluctuates between two pages	Internal relevance conflict	Strengthen primary URL and differentiate support pages
Image traffic drops	Asset, sitemap or lazy-loading issue	Check image URLs and rendered HTML
Mobile crawl stats fall	Server, robots or rendering problem	Review logs, response codes and directives

Do not treat every ranking fluctuation as evidence of cannibalization. Search results change for many reasons, including algorithm updates, new competitors and intent shifts. Look for a sustained pattern supported by overlapping queries, similar content and competing URL signals.

Common Mistakes to Avoid

Assuming responsive design solves everything

Responsive design usually gives you one URL and one content source. It does not guarantee that JavaScript, images, schema or navigation behave properly on mobile.

Hiding important content to improve the layout

Accordion sections and tabs can be useful on small screens, but key information still needs to be available to users and search engines. Test the rendered output rather than assuming the HTML is sufficient.

Copying desktop schema without checking mobile visibility

Structured data should describe content that users can see and understand on the page. Copying a large desktop JSON-LD block into a reduced mobile template can create unsupported or inaccurate properties.

Publishing one article per keyword

This is a frequent cause of keyword cannibalization. Use a keyword clustering strategy that groups close variants around one strong page when the search intent is the same.

Using identical anchor text everywhere

Repeated exact-match anchors can make internal linking look mechanical and fail to explain the difference between pages. Use descriptive, natural anchors that reflect the destination.

Treating canonical tags as a replacement for consolidation

Canonicals can guide search engines, but they do not remove thin content, contradictory metadata or poor site architecture. If two pages serve the same purpose, consider merging or redirecting them.

Ignoring old mobile URLs

Legacy m. pages, AMP pages and campaign variants can remain crawlable for years. Include them in your audit, especially if they have backlinks or historical rankings.

Expert Framework: The Mobile Signal Consistency Score

You can create a simple scoring model to prioritise remediation. Score each URL from 0 to 2 across six categories:

Category	0 points	1 point	2 points
Main content	Major mobile omissions	Minor differences	Equivalent core content
Metadata	Conflicting or blocked	Partially aligned	Semantically consistent
Canonical	Incorrect or unresolved	Technically valid but uncertain	Correct and reinforced
Structured data	Missing or inaccurate	Warnings or partial coverage	Valid and page-supported
Images	Missing or contradictory	Usable but incomplete	Equivalent and crawlable
Internal links	Key paths removed	Reduced contextual support	Clear, consistent architecture

Interpretation:

0 to 4: High-risk mobile indexing and cannibalization issue
5 to 8: Moderate risk requiring targeted fixes
9 to 12: Strong consistency, with routine monitoring still required

This score is not a Google metric. It is an internal prioritisation tool. Use it alongside Search Console data, crawl reports and conversion performance.

Key Takeaways

Mobile-first indexing means Google primarily evaluates the mobile version of your page.
Mobile and desktop pages do not need identical layouts, but they should communicate equivalent core content and intent.
Structured data, metadata, images, canonicals and internal links must support the same URL and entity.
Mobile-specific omissions can create or worsen keyword cannibalization.
A keyword cannibalization audit should compare rendered mobile content, query data, page intent and internal links.
Search intent mapping should come before merging, redirecting or creating new articles.
A strong keyword clustering strategy reduces duplicate topics and builds clearer topical authority.
Schema does not solve duplicate content SEO issues or unclear page architecture.
Image URLs, lazy loading and mobile image variants deserve technical review.
SEO Letters can help you research, cluster, write, structure, publish and refresh content within one repeatable workflow.

Final Conclusion: Make Every Mobile Signal Point to the Same Page

Mobile-first indexing is best understood as a consistency test. Google is trying to identify the page, the entity, the topic, the intended audience and the most useful result. If mobile content, metadata, images, structured data and internal links point in different directions, your site makes that interpretation harder than it needs to be.

The same applies to keyword cannibalization. When similar pages compete without defined roles, every new article can dilute the authority of the pages that already matter. A deliberate content architecture, supported by search intent mapping and a disciplined keyword clustering strategy, gives each URL a clearer job.

If you’re publishing at scale, manual drafting alone will not keep that system organised. SEO Letters helps you move from keyword research to structured, brand-aligned articles, internal links, schema, images and direct publishing, with scheduled campaigns and content refreshes available when you need a more autonomous operation.

Start with one cluster. Audit the mobile version carefully. Then make every ranking signal reinforce the same page.