To check whether a guest post is indexed in Google, inspect its exact URL in the publisher’s Search Console property. Without access, ask the publisher for a dated inspection result. Public searches offer useful clues, but a missing result alone does not prove that a page is unindexed.
An editor sends you the published article. The page opens, your contribution looks correct, and the link works. Those checks establish that the article is live. You still need separate evidence to describe its Google indexing status.
This guide explains what to check, how to record an uncertain result, and which questions help a publisher investigate a missing page. The workflow works for both newly published guest posts and older placements you are reviewing.
What does “indexed” mean for a guest post?
Keep these stages separate in your delivery report:
| Stage | What you are checking |
|---|---|
| Published | The article is available at the agreed address |
| Crawlable | Googlebot can access the page |
| Eligible for indexing | The page meets Google’s relevant requirements |
| Indexed | Google has included a version of the page in its index |
| Appearing for a search | Google shows the page for a particular query |
A working page needs accessible, indexable content and an appropriate successful response to meet Google’s basic technical requirements. Satisfying those requirements does not guarantee inclusion. Google Search technical requirements.
For campaign reporting, maintain separate fields for publication, indexing evidence, and results such as referral visits. This prevents a completed publishing task from being mistaken for a measured search outcome.
1. Start with the exact published URL
Open the address the publisher supplied. Check the browser’s final address after the page loads, and copy it into your placement record.
Record both addresses if the original redirects. A changed category, trailing slash, or updated slug can mean you are checking a different address from the one in the delivery email.
Before investigating Google, review the article itself:
- Does the final page contain the agreed article rather than an error message?
- Can you read it while signed out of the publisher’s account?
- Are the title, author details, and body present?
- Does your link open the correct destination?
- Can readers find the article from an appropriate section of the site?
Send any publication errors to the editor with the affected URL and a specific correction. “The article opens only when I am signed in” is more useful than “the indexing is broken.”
For checks before commissioning an article, use our guide to vetting guest post sites.
2. Use Search Console when you have property access
Select the Search Console property that contains the publisher’s URL, then paste the complete address into URL Inspection. Access to your own business website does not give you access to a publisher’s property.
Read the indexed-page report first. Note the reported indexing status, last crawl when available, and Google’s selected canonical URL. The canonical is the representative address Google has chosen for the content.
The message “URL is on Google” indicates inclusion and eligibility to appear; it does not promise visibility for every query or a particular ranking.
Keep the indexed report separate from “Test live URL.” The former describes Google’s stored information. The latter checks the page now for possible indexing issues. A successful live test does not establish that the page is indexed or predict Google’s canonical selection. Google’s URL Inspection documentation.
In your notes, label which report you used. “Live test passed” and “indexed report confirmed inclusion” describe different evidence.
3. Ask the publisher for a focused report
Most contributors do not manage the publisher’s Search Console account. Ask the editor or technical contact to inspect the page and share the relevant result. A screenshot with unrelated account information removed is usually enough for a first review.
You can adapt this request:
Hi [Name], thanks for publishing the article. Could you check [exact article URL] in your Search Console property and share a dated screenshot of the indexed-page report? Please keep the inspected address, indexing result, last crawl if available, and Google-selected canonical visible. If the page is excluded, please include the reported reason and any planned correction. Unrelated account details can be hidden. Thank you.
Keep the request tied to the particular placement. A screenshot showing the publisher’s overall indexed-page count does not establish what happened to your article.
Check that the address in the evidence matches your record. If the screenshot is cropped too closely or shows only a live test, ask for the missing context. Record “awaiting publisher evidence” while that question remains open.
4. Use public searches as supporting evidence
Without property access, try a Google search restricted to the article’s URL prefix. For example:
site:https://publisher.example/guides/retail-stock-counts/This is an illustrative address. Replace it with the actual published URL, including the correct hostname and protocol. You can also search the article’s distinctive title together with the publisher’s name.
Google explains that site: results are not exhaustive and that even an indexed URL is not guaranteed to appear in these searches. An empty result therefore leaves the status uncertain. Google’s site search operator guidance.
When a result appears, open it and verify the destination. A category page mentioning the title, a syndicated copy, or a different version of the article may not answer the question about your agreed URL.
Save the query, date, and observed destination. Describe the evidence precisely: “Article appeared in this search on this date” is more useful than an undated green tick in a spreadsheet.
5. Investigate the reported reason if the page is missing
Ask the publisher to work from the reason Google reports for the exact URL. Different situations need different responses.
| Reported situation | Meaning and next question |
|---|---|
| Found but not yet crawled | Google knows the URL. Ask whether the publisher has identified a crawl delay or access issue. |
| Crawled but not indexed | Fetching happened without inclusion. Future indexing is uncertain; repeat crawl submissions are not the prescribed fix. |
| Server or access error | Google could not retrieve the page successfully. Ask the technical contact to investigate the response. |
| Page redirects elsewhere | Check the final destination separately and update the delivery record. |
| Duplicate or alternate version | Inspect the representative URL and confirm whether that relationship is intended. |
These are simplified descriptions; preserve the exact reason from the publisher’s report in your notes. A non-indexed URL can be intentional, especially when it duplicates another page. Google’s Page indexing report guidance.
Check whether a noindex instruction is intentional
A noindex instruction in a robots meta tag or an HTTP response header can prevent inclusion after Google processes it. The publisher should check both locations when investigating an unexpected exclusion.
Google must be able to crawl the page to see that instruction. Blocking crawling with robots.txt does not reliably remove a URL from search and can prevent Google from seeing its noindex rule. Google’s noindex documentation.
Ask whether exclusion matches the publishing agreement. Let the site owner correct an unintended setting; some pages are deliberately kept out of search.
Check an unexpected canonical destination
A declared canonical expresses a preference for the representative version. It does not force Google’s selection. Conflicting signals, such as a sitemap and canonical annotation pointing to different versions, deserve review. Google’s canonical URL guidance.
For example, suppose the delivered address contains a campaign parameter while the clean article URL is the intended representative. Record that relationship and verify the clean version. If the reported destination is an unrelated article, send both addresses to the publisher and ask for an explanation.
6. Agree on a follow-up after a correction
Once an actual issue has been corrected, an owner or full user of the relevant property can request indexing through Search Console. You cannot submit a publisher’s URL through your own site’s property simply because it links to you.
Google says crawling can take days to weeks. A request does not guarantee immediate inclusion, and submitting the same URL repeatedly does not make crawling faster. Sitemaps can help Google discover URLs, but are not proof that those URLs were indexed. Google’s recrawl guidance.
Set a practical review date with the publisher. Record the change made, when it went live, who will check again, and what evidence they will provide. This gives both parties a clear next action without inventing a Google deadline.
For an older article, also ask whether its address, access rules, or content recently changed. The placement history helps you distinguish a new problem from a question that was never resolved at delivery.
Keep an indexing evidence log
Use a short record for each placement:
| Field | What to save |
|---|---|
| Delivered and final URL | Both addresses if they differ |
| Publication check | Date, page availability, and any delivery errors |
| Evidence source | Publisher report, your authorized inspection, or public search |
| Evidence date | When the observation or report was obtained |
| Report details | Status, reported reason, last crawl, and canonical when available |
| Open action | Specific question or correction and responsible contact |
| Next review | Agreed date and the evidence still needed |
Consider this illustrative case: an article opens normally, a public search returns no match, and the editor has not yet supplied a report. Your record should show published; indexing unconfirmed. It should not jump to either “indexed” or “failed.”
If the editor later supplies a dated indexed-page report, add the new evidence and retain the earlier observation. A simple history makes delivery disputes and subsequent changes easier to understand.
Common questions about guest post indexing
Does a dofollow link prove the article is indexed?
No. Link attributes and page indexing are separate checks. The informal term “dofollow” does not certify inclusion. Similarly, an article containing a nofollow link can still be indexed. For paid links, Google prefers sponsored; nofollow is also acceptable. Google’s link attribute guidance.
Check the agreed destination and anchor text alongside indexing evidence, keeping each result in its own field.
Does the publisher’s homepage appearing prove my article is indexed?
No. Your evidence needs to identify the article under review. A homepage result and a domain-level report answer different questions. Ask for the exact address rather than accepting a general claim about the website.
What should an indexing guarantee specify?
Ask the provider to define the evidence it accepts, the review period, and any replacement or refund conditions. Keep that agreement with the placement record. A commercial remedy does not give the provider control over Google’s decisions.
When comparing guest posting with link insertion, apply this same evidence standard to both new and existing articles. A clear report should show what was published, what was observed, and what still needs attention.
