How to Fix Google Ads Sitelink Assets

To fix Google Ads sitelink assets, identify whether the problem is visibility, approval, association, destination, schedule, relevance, or downstream performance; then check the evidence in that order and change the smallest responsible part. A sitelink that is not visible may have a serving or scope issue, while a sitelink that receives clicks but produces poor leads may have a message or landing-page problem. Do not solve both symptoms by rewriting everything at once.

Google’s current sitelink asset help covers creation, associations, schedules, removal, and troubleshooting. Its eligibility explanations matter: a saved sitelink is not guaranteed to appear on every ad, and Google may choose from eligible assets based on context and predicted performance. Start with the actual status and effective set before assuming the copy is the cause.

Identify the symptom before changing the asset

Write down what the team observed, where it was observed, and the expected behavior. “The link is missing from one mobile preview” is different from “the asset is disapproved,” “the campaign inherited a regional link,” or “the link gets clicks but no qualified outcomes.” Capture the campaign, ad group or asset group, device, time range, label, URL, and association level.

When the sitelink does not appear

Check status, campaign and ad-group state, effective associations, device requirements, the number of eligible links, schedule overlap, duplicate or similar text, URL requirements, and whether the preview represents the branch you edited. Google can choose not to show a sitelink even when it is approved if another set is predicted to perform better or if the display context does not support it.

Do not use one search result as proof that the asset is broken. A live search is affected by query, location, device, auction, personalization, position, and timing. Use the account’s asset status and reports as the primary evidence, then use previews or a controlled manual check to confirm the experience.

When the asset is disapproved or limited

Read the policy reason and inspect the wording, destination, domain, offer, trademark use, punctuation, and landing page. A label can be disapproved for what it says, where it sends people, or how it relates to the advertised business. “Approved” and “Approved (limited)” are different from a fully unrestricted serving expectation; record the exact state before editing.

When clicks are weak or outcomes are poor

Separate low delivery from low engagement and low post-click quality. A sitelink with few impressions needs a coverage, schedule, eligibility, or relevance check. A link with impressions but few interactions needs a label, set, or context review. A link with interactions but weak leads or sales needs a full path review of intent, page, form, checkout, tracking, and qualification.

Check status and policy evidence first

In the current Google Ads interface, open Campaigns and Assets, then inspect the asset’s Status column. Add the Policy details column when it is available in the table. Google’s review-status guidance describes statuses such as Under review, Approved, Approved (limited), and Disapproved; use the status and policy details to decide the next check rather than relying on a screenshot or an old email.

If the asset is under review, avoid repeatedly editing it without a reason: an edit can restart review. If it is disapproved, read the linked policy, correct the relevant text or destination, and submit the changed asset for review or appeal through the documented process. Keep the original reason and new version in the campaign record.

Review the destination as part of the policy issue

Open the final URL directly, on mobile and in the intended region. Confirm it loads for normal users, is crawlable where required, uses the expected domain, and contains the offer or content named by the sitelink. Check redirects, login gates, consent, broken forms, phone routes, inventory, and unavailable appointments. A policy or delivery problem is not fixed if the label changes but the page remains wrong.

Google’s sitelink asset requirements cover repeated link text, third-party domains, unnecessary punctuation, and relevance. Make the underlying content compliant instead of using vague copy to hide a mismatch. For a third-party destination allowed under a limited exception, make the destination clear in the text as the current policy requires and verify that the use is appropriate for the account.

Check association level and inherited assets

Open the asset table’s association view when available. Confirm whether the sitelink is attached to the account, campaign, ad group, or asset group that you intended, and check any additional associations. Then inspect a representative ad group or asset group in the same branch. Higher-level sitelinks can remain eligible with lower-level links when Google predicts they may help, so the asset list you edited may not be the complete effective set.

Fix an over-broad association

If a product, location, price, or promotion appears in an unrelated campaign, remove the shared association or replace it with a link whose promise is truly universal. Move a campaign-specific link to the campaign, ad-group, or asset group where its audience and page match. Before removing an account-level asset, check other branches so a fix for one campaign does not silently remove a useful universal link elsewhere.

If one asset is used by several branches and only one needs a different label or URL, create a separate asset for the exception. Editing a shared asset can change every association, which may create a new problem while solving the first one.

Fix missing or inconsistent delivery

Once status and association are known, compare the asset schedule with the ad and campaign schedule. Check start and end dates, days, hours, time zone, paused state, location, device, and the time range used in the report. A link can be valid but ineligible during the impression you are trying to inspect.

Check the effective set for repeated or very similar labels. Google’s help notes that unique text helps more links serve together and that sitelinks may not appear when duplicate URLs, third-party requirements, or other conditions are not met. Replace a duplicate with a genuinely useful destination, or remove it if the set already answers that question.

If all checks pass but delivery remains lower than expected, add only a relevant alternative and give the set time to collect data. Do not keep re-uploading or editing an approved asset simply to force an impression. A low predicted performance is a signal to review intent, label, destination, and context—not a guarantee that a new version will serve.

Fix the preview mismatch

Confirm that the preview uses the same campaign, ad group, device, location, language, and date context as the asset you changed. A preview can show a different eligible set from another branch. Compare its URL and labels with the association report, then reproduce the issue with the smallest controlled set of conditions possible.

Do not make decisions from a personalized live search. Search results vary by auction and user context, and an ad preview is not a promise that an asset will show in every auction. Use the account’s status and reporting for the diagnosis and document the limitation in the ticket or change record.

Fix URL, label, and page mismatches

If the label says “Pricing” but the page only offers a generic contact form, choose one repair: change the label to match the page, or fix the page so the pricing promise is fulfilled. Do not leave a misleading combination in place while waiting for a larger site project. The same rule applies to locations, availability, comparisons, support, features, and promotional claims.

Check the final URL rather than only the string in the editor. Test redirects, parameters, canonical behavior, mobile layout, regional routing, cookie and consent flows, login requirements, phone links, forms, and checkout. If the page is temporarily unavailable, pause the sitelink or use an honest fallback until the destination is restored.

Repair policy-related text

Remove repeated link text, decorative punctuation, unsupported claims, and unclear wording. Confirm that a third-party URL is allowed for the use case and that the link text explains the destination as required. Check trademarks and the content of the linked page as well as the asset field. A cosmetic change that leaves the same misleading claim will not solve the root issue.

After saving the correction, review the policy detail and status again. Keep a copy of the old and new wording, the reason for the change, the reviewer, and the next check. If the decision is still wrong after the content is compliant, use the documented appeal route instead of creating many nearly identical assets.

Fix clicks that do not become useful outcomes

Start with the path: search query or audience, primary ad, sitelink label, destination, device, location, page interaction, form or checkout, consent, and qualified outcome. Compare the click intent with the page’s first visible message. A label that attracts curiosity but not the intended buyer may need more precise wording or a different destination.

Check the measurement implementation before changing copy. Confirm the conversion event fires once, tracking parameters survive redirects, consent requirements are respected, phone and form events are recorded, and sales or lead-quality data can be joined to the campaign. A missing downstream result can be an analytics problem rather than a sitelink problem.

Use enough data for the decision

Review impressions, interactions, spend, conversions, qualified rate, value, and conversion lag by link and campaign where the data supports it. A low direct conversion rate does not automatically make a research or proof link bad; it may assist a later action. Conversely, a high interaction rate can be negative if the label sends unqualified visitors into an expensive sales process.

Use the normal lag and a stable comparison period. Annotate changes to bids, budgets, primary ads, audiences, pages, offers, inventory, and seasonality. When the evidence is weak, choose “wait” with a next review date rather than making a permanent removal based on noise.

Verify the repair and define rollback

After changing an asset, recheck the fields, association, schedule, URL, status, policy detail, and effective set. Preview a representative ad and open the destination on mobile. Confirm that the asset did not change another campaign through a shared association. Record the time and the exact version that was published.

Define a rollback condition before the new version runs: a broken URL, expired offer, policy regression, irrelevant branch, qualified-rate decline, or value loss after a fair observation window. Preserve the prior label, URL, scope, and description so rollback is a deliberate restoration. Do not roll back a temporary review delay as though it were a performance failure.

Escalate when the evidence is unclear

Escalate a policy question to the appropriate policy or legal owner. Escalate a broken page to the site owner. Escalate tracking discrepancies to analytics, and account-interface or serving anomalies to the person who manages the Ads account. Include the asset ID or label, campaign branch, status, URL, time range, screenshots or exports, and the smallest reproduction steps.

An escalation record should state what is known, what is uncertain, what has already been changed, and what must not be changed while the issue is being investigated. This prevents several people from editing the same shared asset and losing the evidence needed to find the cause.

Google Ads sitelink troubleshooting checklist

Work through this list before closing the issue:

[ ] The symptom, campaign branch, device, time range, label, URL, and expected behavior are recorded.
[ ] Status and Policy details have been checked in the current Assets view.
[ ] Under-review, disapproved, approved-limited, and campaign-paused states are not being conflated.
[ ] The final URL, redirects, domain, mobile page, form, call, checkout, login, consent, and offer have been tested.
[ ] Repeated text, similar labels, punctuation, relevance, trademarks, and third-party destination rules have been reviewed.
[ ] Account, campaign, ad-group, and asset-group associations and inherited sitelinks have been inspected.
[ ] Asset and ad schedules, time zone, campaign status, device, and location conditions overlap as intended.
[ ] Weak delivery, engagement, and downstream quality have been separated.
[ ] Tracking, conversion events, qualified outcomes, value, and lag are reliable enough for the decision.
[ ] The smallest repair, owner, review date, and rollback condition are documented.

For prevention and ongoing review, see Google Ads sitelink assets best practices. For the initial association workflow, read how to set up Google Ads sitelink assets. The adz.so product overview describes the current audit entry point; it does not claim that adz.so fixes or publishes Google Ads sitelinks automatically.