Make each additional link serve a clear customer decision
Google Ads sitelink audits for freelancers: review relevance, descriptions and the actual attachment scope
Check what the sitelink findings establish, connect each link to a useful destination and prepare precise owner-approved changes. Keep asset content, campaign attachment and observed appearance separate.
Define the freelance sitelink brief
A sitelink audit should begin with the client's intended decision. The owner may want better navigation for a Search offer, a review of inherited links or a precise repair to incomplete descriptions. Those questions overlap, but they are not identical. Record the campaigns, business offers and destinations under review, then clarify whether the engagement includes recommendations or live implementation. A freelancer should know what the client wants to improve before treating every asset finding as a request to create more links.
Ask who can approve the commercial content and who owns the website. A sitelink may describe delivery, booking, a product range or a service guarantee. The business owner needs to confirm those facts, while the website owner may need to repair the destination. The freelancer can coordinate the review without pretending every part belongs to the account tool. A useful brief makes those responsibilities clear and avoids a proposal that changes an ad asset while leaving its underlying page unresolved.
Set a manageable scope. If the client asks about one campaign, investigate its relevant branch and the shared assets that could affect it. Do not silently expand the work to every campaign in the account. The final report should say what was inspected, why a link is useful or unsuitable, which action was approved and what was verified. This gives the freelancer a defensible deliverable and gives the client a decision record that remains understandable after the Slack conversation has ended.
Choose useful customer journeys
A sitelink should give the intended visitor a useful route beyond the main ad destination. Start with the customer decisions the business actually supports: choosing a service, checking availability, booking a consultation or understanding delivery. The label and page should answer that decision coherently. A freelancer reviewing a specialist campaign should not fill its links with unrelated navigation merely because those pages exist. Relevance to the advertised offer matters more than the convenience of copying a website menu.
Map each proposed link to a concrete purpose. A retailer's product category may help a customer narrow the range, while a booking link may suit a service campaign. A policy or help page can be useful where it resolves a genuine purchasing question. The owner should understand why the link belongs in the selected campaign. This also makes later maintenance easier: when the business changes, the purpose provides a clear basis for retaining, revising or removing the link.
Do not assume the same links suit every campaign. A wholesale offer and a consumer offer can share a domain while needing different customer journeys. An account-wide attachment may be inappropriate for a page intended only for a specialist audience. The freelancer should confirm the relevant scope before recommending reuse. A small set of purposeful destinations can provide a stronger review than a long inventory of familiar pages that the owner cannot connect to the actual campaign.
Separate coverage from content completeness
ppctor has a core-asset coverage finding and a separate sitelink-description finding. Coverage asks whether the relevant asset type is applied through the account or campaign arrangement inspected. Description completeness asks whether the counted linked sitelink assets have both description lines. A freelancer should preserve these questions in the explanation. A campaign can have a sitelink arrangement whose content needs improvement, and the absence of a description card is not automatically proof that sitelinks are present.
The description card is hidden when the reader counts no linked sitelinks. Their absence belongs to the coverage investigation. When linked sitelinks are counted, the card reports complete or incomplete descriptions and lists the affected link text. This structure should not be translated into a universal certificate of good navigation. The checks establish particular configuration observations. Commercial usefulness, destination quality and actual appearance require their own evidence when the client asks about them.
Explain the distinction with the actual client problem. If no relevant link is applied, investigate the appropriate attachment. If the link is present but unhelpful, review its text and page. If descriptions are absent, prepare the appropriate content decision rather than creating unrelated extra assets solely to clear a warning. A precise diagnosis reduces unnecessary edits and helps the owner approve the operation that addresses the real problem.
Understand the asset and association reads
The current extension reader obtains enabled account associations, enabled campaign associations under enabled campaigns excluding Local Services and Smart, sitelink asset content and the selected served-campaign population. Sitelink descriptions are read directly from the asset resource and joined by asset identity. This matters because an association establishes where an asset is applied, while the asset contains its link text and descriptions. The reader does not need to infer description content from a campaign relationship row.
The served-campaign population uses impressions in the selected reporting window for the coverage assessment. That population is not the same as every campaign with an enabled sitelink association. The linked-sitelink collection combines the enabled account associations and qualifying campaign associations, and the description check then examines the distinct linked assets. A freelancer should not describe the description count as a count of only those links that actually appeared during the selected period.
The broader extension reader performs additional logo-related reads only when the relevant channel population requires them. Those queries should not be mistaken for extra sitelink inspections. Keep the explanation tied to the surfaces needed for the question. A quick sitelink finding can support a focused review without implying that the tool has fetched every lower-level association, live landing page or asset-performance segment in the account.
Interpret distinct-asset counts
The reader stores linked sitelink resource identities in a set. One asset attached to several campaigns is therefore counted once in the description population. This is a count of distinct linked assets, not a count of campaign attachments, rendered links or clicks. A freelancer should use that exact meaning when explaining “two incomplete sitelinks.” The same two assets may have a wider attachment footprint, and that footprint matters to the review of a shared-content change.
Different assets can have the same visible text. Their URLs or descriptions may differ, so identical labels do not establish that the assets are interchangeable. The compact finding lists link text and missing-line status rather than every resource relationship. Resolve the actual asset before preparing a content operation or attachment change. A human-readable label helps the owner recognise it, while the internal target supports precise execution behind the scenes.
Do not sum asset and association counts into an impressive but ambiguous total. A report can show distinct assets, affected campaigns and proposed changes separately where those figures are actually read. That gives the client useful context without conflating different populations. If the owner asks how widely one asset is reused, inspect its relevant associations. The description count alone cannot answer that scope question, even when the same text appears familiar across several campaign views.
Investigate missing description lines
The current description calculation checks whether description one and description two are truthy in the returned asset content. It records one or two missing lines and sorts the incomplete list by that count, then by link text. This is a presence check. It does not evaluate whether a filled line is accurate, persuasive or useful. A freelancer should review the actual wording before presenting a complete description as commercially adequate.
Google's sitelink guidance recommends descriptions and explains that their inclusion can make the asset eligible for additional detail. It does not mean every filled line will always be shown. Treat the missing-line finding as a content opportunity, then write descriptions that explain the actual destination. Do not promise a fixed increase in click-through rate merely because two fields become populated.
Use the business purpose to choose what each line contributes. The first might clarify the page's offer and the second its intended next step, but that is a writing choice rather than a universal formula. Avoid repeating the link label without adding useful information. The owner should be able to read the proposed lines and recognise the page they describe. A complete pair of truthful descriptions is more valuable than filler text inserted only to make the audit show complete.
Review the relevant hierarchy
Google describes sitelinks at account, campaign, ad-group and asset-group levels, with eligible links in the same hierarchy branch able to serve together. Do not assume a campaign-level link automatically suppresses the account-level link. The current description reader collects account and campaign associations; it does not comprehensively inspect lower-level sitelink arrangements. A freelancer should state that boundary when the client asks about one specific group or a complete inheritance inventory.
Choose scope according to the business relevance of the destination. An account-level delivery page may suit all eligible retail campaigns, while a specialist booking page may belong only to the campaigns offering that service. The owner should understand where the recommendation applies. A hierarchy decision is not merely a technical preference. It determines which offers can draw from the selected link arrangement and therefore needs commercial review before the association is changed.
A detachment at one level should not be described as removing the link everywhere. The asset may remain attached through another level or another campaign. Inspect those relationships when the client requests a global removal. The freelancer can propose a narrow campaign detachment for a narrow problem while explaining what is retained. Clear scope prevents the owner from expecting a sitewide or account-wide effect from an operation that changes only one selected association.
Write a recognisable link label
The label should make the destination recognisable to the intended visitor. Use the business's actual offer rather than a generic action that could describe any page. A freelancer can ask what a customer expects after clicking and compare that expectation with the page. If the destination is a consultation booking form, the label should not imply an immediate purchase. If it is a product range, avoid making it sound like a customer-support route.
The current convenience creation validates a non-empty sitelink label of at most twenty-five characters. That local validation boundary does not guarantee provider acceptance in every language or prove that the wording is useful. Keep the actual supported preparation and provider decision separate. The owner should review the commercial meaning and clarity, while the tool handles the declared field requirements. A shorter label can still be misleading if it promises the wrong page or offer.
Review similar labels together. Two links that appear interchangeable to a customer can make navigation confusing even if they lead to different pages. The freelancer should identify the distinct decisions they serve and write accordingly. Do not produce a large set of near-duplicate labels merely to increase the apparent asset inventory. A useful audit explains why each link belongs and how a customer can choose it, rather than judging the arrangement only by the number of text strings created.
Use descriptions to explain the next step
Descriptions should add relevant information the label cannot carry. Confirm the page's offer, conditions and next step with the owner before drafting. A business can provide appointments, fixed-price products or an enquiry process; those differences matter. Avoid inventing delivery speed, discounts or guarantees to make the lines seem more attractive. The freelancer's creative contribution should clarify confirmed facts rather than manufacture claims that the destination does not support.
Drafting descriptions can stay conversational. The assistant can suggest wording from the supplied offer without performing a provider request merely to write copy. Those suggestions should remain clearly distinct from observed account content. When the owner selects the desired text, resolve the actual asset and supported edit route before preparation. A creative draft does not establish that the asset already contains it, and a request for ideas does not authorise a live change.
Review both lines together with the label and destination. Each part should describe the same customer journey. A description that belongs to a different service can be more problematic than an empty field because it creates an expectation the page cannot satisfy. The audit presence check cannot evaluate that coherence. The freelancer should document the content decision and owner confirmation so the eventual implementation reflects the business meaning the client actually approved.
Confirm the intended destination
The final URL should lead to the specific page described by the label and descriptions. Ask for the relevant destination when it is not already established. Do not substitute the homepage silently because it is the only address visible in the conversation. A business can share one domain across several offers, and the selected campaign needs the appropriate route. The owner should review the actual URL in the proposal alongside the content that introduces it.
The convenience creation normalises supplied URLs and checks their public-page form. It requires at least one final URL. This is configuration validation, not a live certification of page reachability, content or customer experience. The freelancer should inspect the destination where that work is in scope and assign any website repair to its owner. A URL accepted by the provider does not by itself prove that visitors can complete the intended booking or purchase journey.
Keep website and account completion separate. A developer may fix the destination while the freelancer prepares a campaign attachment. The client should see the acceptance evidence for each task. If the page is still incomplete, retain that outstanding dependency instead of reporting the navigation repaired because the asset exists. A precise handoff explains what was configured, what was inspected live and which remaining business or website decision is needed before the intended experience can be considered ready.
Review changing offers and schedules
A link can become unsuitable without any field becoming empty. A promotion can end, a booking window can close or a product range can be discontinued. The freelancer should ask which offers are permanent and which are time-sensitive. An audit of description presence cannot answer that question. A useful recommendation identifies the commercial condition that determines whether the link should remain eligible, be revised or be detached through the appropriate supported route.
Scheduling is a separate configuration concern. The dedicated creation and attachment convenience actions inspected for this workflow should not be presented as a universal sitelink-scheduling editor. If the client requests a start date, end date or daypart arrangement, verify the current appropriate setting capability and target before promising an operation. The existence of provider scheduling options does not mean this particular preparation tool has selected or written them.
Give the owner a maintenance trigger. A temporary course link can be reviewed when enrolment closes; a delivery page can be reviewed when the service conditions change. This makes the freelance handoff useful after the initial edit. Do not rely on a future audit to discover every commercial change automatically. The owner knows when an offer changes, while the tool can support the relevant targeted inspection and approved configuration update once that change has been identified.
Separate eligibility from appearance
An enabled association makes an asset part of a configured eligible arrangement, subject to the relevant provider rules. It does not establish that the link appeared in every ad impression. Google chooses among eligible assets and formats, so a stored asset and an observed appearance are different facts. The freelancer should not promise a particular rendered layout simply because the attachment read succeeds or both description lines are filled.
If the owner asks why a sitelink is not visible, inspect the appropriate current conditions and performance evidence rather than declaring the attachment broken from one manual search. The commercial relevance, hierarchy, policy and actual campaign activity can all matter to the investigation. A targeted question needs targeted evidence. The audit can establish configuration presence, but it should not be extended into a guarantee about every device, placement or individual auction the client happens to observe.
Keep visual examples illustrative when explaining the intended arrangement. A proposed label and description can help the owner understand the content, but it is not a screenshot of guaranteed delivery. The freelancer should avoid presenting a mockup as a provider-confirmed result. A good review can state that the desired content and attachment were verified while leaving actual appearance to the relevant reporting observation. This makes the success claim accurate without diminishing the value of the completed configuration work.
Read performance without inventing impact
If the client wants a performance review, define what the asset metrics represent before interpreting them. Activity when an asset appeared and clicks on a particular link are different reporting questions. The description audit does not itself obtain a complete asset-performance analysis. A freelancer should request the supported relevant evidence rather than infer financial impact from the number of incomplete descriptions. A structural opportunity is not a measured revenue loss.
Preserve the requested period and conversion definition. Standard primary conversions can aggregate several primary actions; purchase-only or named-action questions need the corresponding selection. A sitelink directing visitors to a contact page may have a different business role from one directing them to a product category. The owner should understand the metric used for comparison. Do not casually treat every conversion value as an order or sum incompatible populations merely because the report contains monetary values.
A later improvement needs proportionate interpretation. Other ads, auctions, budgets, seasonality and website changes can affect results. Record the sitelink operation and its verification date, then assess subsequent evidence without claiming a controlled experiment that did not occur. The freelancer can demonstrate useful work and observed changes while avoiding a guaranteed uplift formula. This is especially important when a small number of clicks would make a confident ranking of assets look more precise than the actual evidence supports.
Choose the actual supported operation
The inspected conversational convenience builder can create and attach a new campaign sitelink, attach an existing suitable asset or detach an existing campaign association. It validates the selected asset type for reuse and requires a readable asset name or content for review. These are campaign-targeted operations. Do not describe them as automatic global sitelink replacement or a universal existing-description editor. The desired content change needs its current appropriate supported route.
Creation stores the asset and its campaign relationship in a combined provider mutation with partial failure disabled for that request. Existing extensions are retained. This is an additive operation, and the proposal should say so. Attaching an existing asset reuses it rather than copying its content. Detaching changes the selected relationship while retaining the asset itself. The owner should understand which alternative is proposed before confirming the live edit.
If a requested attachment already exists, or a requested detachment is already absent, the convenience preparation can return without adding a mutation. That should be explained as the requested association state already existing, not as an invented new change. A freelancer should also consider other hierarchy levels when the client wants the link removed completely. The selected campaign operation alone cannot establish that no other account or lower-level association remains eligible.
Follow an invented freelance review
Consider an invented freelancer, Elise Vale, reviewing an invented business called Birch Lane Courses. This is an illustrative scenario, not a customer account or a claimed result. The owner asks for better links in one evening-course campaign. Elise records the campaign and reviews the detected sitelinks. She distinguishes an incomplete shared asset from a campaign-specific missing destination and asks which pages the owner wants visitors to use.
The owner confirms that a general course catalogue is useful across the business, while an evening booking page belongs only to the selected campaign. Elise does not change the shared asset's content as though it were private to that campaign. She drafts truthful descriptions for the agreed destinations and prepares the appropriate supported campaign creation-and-attachment proposal for the new link. The proposal makes clear that existing extensions remain and that the new URL still needs the website owner's confirmed page readiness.
After owner confirmation, the relevant checks establish the new asset content and campaign relationship. Elise reports those configuration results without promising that both descriptions will appear in every impression. She leaves the shared-content question and website evidence with their assigned owners. At follow-up she inspects the actual relevant activity if the client requests it. The example demonstrates a useful freelance sequence: understand the journey, inspect scope, approve the precise operation and verify only the states actually checked.
Use Slack for creative and evidence
Start with a scoped question: which linked sitelinks have missing descriptions, or which links are attached to the selected campaign. The assistant should use the relevant supported evidence and preserve the established context in follow-up. If a visible label matches more than one asset, resolve the intended destination and target before preparation. A fluent conversation should reduce repeated broad questions while retaining the exact selection necessary for a live change.
Creative suggestions can stay conversational. The assistant can write candidate labels and descriptions from the confirmed page purpose without querying Google Ads merely to brainstorm. Current stored content and attachments need account evidence. Keep those two activities distinct in the response. An invented draft should not be described as an existing asset, and a request for wording ideas should not trigger creation. This makes the tool useful for normal discussion as well as evidence-based operations.
Show multi-step requests as clear logical actions and stay within the current three-action limit. Creating and attaching one supported extension can have its related technical dependencies handled by the prepared operation, while separate requested detachments or other edits still need to be visible. If the owner asks for more than the limit, split the request into smaller reviewed proposals. Do not silently omit a requested removal while reporting the whole navigation update as complete.
Review the proposal before execution
The confirmation should identify the campaign, selected existing asset or new content, final URL and exact action. A creation proposal should show the link label and descriptions in readable rows, with attachment clearly stated. A detachment should name the relationship being removed and explain that the asset is retained. Normal client output should use recognisable names and content, while internal asset references remain part of the reliable targeting logic behind the scenes.
Read the complete intended effect before pressing Confirm and Execute. The proposal should state that no changes have been made yet and that it has a limited expiry. A conversation about descriptions or a request for suggestions is not a live-edit confirmation. The freelancer can help the owner assess scope and wording while keeping this boundary explicit. A single confirmation is useful when every logical action is clear, not when it hides several different operations in one technical paragraph.
Check whether the client expects addition, replacement or removal. The convenience creation retains existing extensions, so it should not be presented as replacing an old link automatically. Campaign detachment does not erase the asset or guarantee it cannot appear through another relevant association. The owner should recognise these effects before approval. Successful execution of an incorrectly described proposal is still a poor client outcome, even when every provider request and field check behaves exactly as implemented.
Verify content and attachment separately
The new-extension preparation builds readback checks for written content leaves, final URLs and the exact enabled campaign attachment using the created asset reference returned by the provider. These checks establish different parts of the requested configuration. A stored sitelink without the intended relationship is not the same as a completed campaign addition. The freelancer should report the confirmed content and association together only when the appropriate evidence supports both.
Existing attachment and detachment checks concern the selected campaign's enabled association population. They establish the requested relationship change, not a global content edit or an account-wide removal. Keep that scope in the client report. A broad subsequent description pass can be useful context, but it is not a substitute for the exact target checks when the owner asks whether the approved operation happened. A distinct asset count cannot prove every association was updated as intended.
Configuration verification remains separate from policy approval, live destination inspection and observed appearance. The final executed-and-verified message should make the completed operation visible without claiming those other states were checked. The freelancer can then assign any remaining evidence to the appropriate owner or follow-up. This separation gives the client confidence in the implemented change and a clear understanding of what further observation is needed for the wider customer-experience or performance question.
Reconcile uncertain changes
If a change was sent but complete verification failed, do not assume nothing changed. Read the relevant asset and campaign association, compare them with the approved plan and establish what remains outstanding. Blindly repeating creation can add another asset rather than repair a missing observation. The freelancer should keep the exact desired content and target available for reconciliation, instead of restarting with a vague request to fix sitelinks.
Distinguish provider rejection from incomplete readback. A rejected operation and an accepted operation whose later check failed need different next steps. The owner should receive a concise account of what is known and which inspection will establish the final state. Avoid replaying a whole multi-step request when only one part remains uncertain. Once the current configuration is established, prepare any genuinely remaining action through a fresh clear proposal where needed.
Do not use an audit fallback to close uncertainty. A generic missing-description label from an unmatched asset row is not proof that the created content is blank. A smaller incomplete count is not direct proof of the intended association. Use the exact relevant target evidence. This makes incident resolution efficient and protects the client from duplicate or unnecessary edits triggered by a broad summary whose population does not match the disputed operation.
Leave a readable client handoff
The handoff should connect each link to its business purpose, destination and scope. State the observed content issue, chosen operation and verified outcome separately. A compact table can show the label, page, intended campaign and next owner action. Keep provider fields, raw resource names and technical retrieval timestamps out of the normal client explanation unless they are necessary to understand a concrete limitation. The owner should be able to assess the navigation in ordinary language.
Use precise totals. Distinct linked assets, incomplete assets, affected campaigns and proposed operations are different counts. Report only those supported by the actual inspection. If a fuller supported output is provided, preserve the same date scope and definitions used in conversation. The report should not turn a configuration inventory into an invented performance claim or imply that a short Slack preview represents every lower-level relationship in the account.
Link related work where it answers a specific question. A disapproved-ad review can help organise a separate policy issue, while the wider audit workflow provides other account context. Keep the sitelink conclusion intact. A focused freelance review can be complete within its agreed scope without claiming to certify the entire website, all advertising assets or every measurement condition.
Maintain relevance as the business changes
Choose follow-up according to the actual change. A new link needs its configured content and attachment confirmed, with destination readiness checked by the appropriate owner. A seasonal link needs a clear review trigger. A shared-content recommendation needs its reuse scope considered before implementation. These are practical maintenance decisions, not a promise that every future commercial change will be detected automatically by the description-presence card.
If the owner wants a later performance assessment, define the relevant period and metrics, then obtain the supported evidence. Preserve the distinction between appearing with an ad and receiving a click on the individual link. Do not attribute every later improvement to the new descriptions without appropriate evidence. The freelancer can document the verified intervention and report actual subsequent observations while keeping the strength of the conclusion proportional to the amount and type of data returned.
Close the engagement with a reusable record: the journeys reviewed, the actual audit boundaries, owner-approved content, target relationships, verified configuration and any separate website or policy work. This gives the client a clear basis for maintaining the arrangement. The value of a sitelink audit is purposeful navigation and precise implementation. It should leave more than populated description fields: it should leave an understandable explanation of why each link belongs, where it applies and what was actually confirmed.