Your guest post is live. You can open it in a browser, the link is in place, and the publisher has confirmed the job is done. But when you look for it in Google, nothing comes up. So is the page not indexed by Google, or just not showing yet?
The short answer: a live article can still be missing from Google's index for four common reasons. Google may not have crawled it yet, the page may block indexing, Google may treat it as a duplicate of another URL, or Google may have seen it and decided not to index it for now. Before you change anything or chase the publisher, check the exact URL and find out which of these applies.
Three terms used below. To crawl a page means Google's crawler fetches it. To index a page means Google stores it so it can appear in search results. The canonical URL is the version Google picks as the main one when several URLs show the same or very similar content.
Start with the URL Inspection tool in Google Search Console, and inspect the exact URL of the article, including the right protocol, subdomain and trailing slash.
The tool shows two different things, and it helps to keep them apart:
Don't rely on a normal search or a site: query to settle the question. Google says an indexed URL is not guaranteed to appear in site: results, so not finding it there proves nothing either way.
And keep indexing and ranking separate. "URL is on Google" means the page is eligible to appear. It does not mean it will rank, get traffic or pass any particular value through its links.
If the article is not indexed, work through these four checks in order. They are a starting point, not a full technical audit.
What to inspect: in URL Inspection, look at whether crawling was allowed, whether the page fetch succeeded, and whether Google ran into a server error, a redirect problem or a login wall.
What it can mean: a page that loads fine in your browser can still fail for Googlebot. Firewalls, bot protection, a server that times out, or content behind a login can all stop the crawler while human visitors see nothing wrong.
Next action: if the fetch fails, run the live test to see whether the problem still exists. If it does, the fix sits with whoever runs the server or the site.
What to inspect: look for a noindex rule, either in the page's meta robots tag or in an X-Robots-Tag HTTP header. URL Inspection reports this under indexing allowed.
What it can mean: a noindex rule tells Google to keep the page out of its index. Sometimes that is deliberate. Sometimes a template, a plugin setting or a staging configuration adds it by mistake.
Robots.txt works differently: it controls crawling, not indexing. If robots.txt blocks the URL, Google cannot fetch the page, so it never sees a noindex rule on it. A blocked URL can still end up indexed without its content if other pages link to it.
Next action: only remove a noindex rule if the page is meant to be indexed. If you need Google to read noindex, the page must not be blocked in robots.txt.
What to inspect: compare the user-declared canonical with the Google-selected canonical, where the tool shows both.
What it can mean: if Google picked another URL, it sees your article as a duplicate or an alternate version of that page. That can be intended, for example a print version pointing to the main article. Or it can be unexpected, such as the same text published under two addresses, or a tracking-parameter version treated as the main one.
Next action: a canonical declaration is a signal, not an order. Google takes it into account but may choose differently. If the wrong URL was selected, look for duplicate copies and make sure internal links and the sitemap point to the version you want indexed.
What to inspect: the last crawl date, compared with the publication date and the date of any fix.
What it can mean: if Google last crawled the page before it was published or before a problem was fixed, the stored data still shows the old state. All the information in the indexed result comes from that last crawl.
Next action: once the live test passes, the site owner can request indexing. Google notes that sending the same request repeatedly will not get a URL crawled any faster, so one request is enough.
The Page indexing report uses two statuses that are easy to confuse:
Neither status is a penalty, and neither points to a single cause. Treat them as a reason to review the page, not as an error to fix with one change. Areas worth checking:
Improving these areas can help, but none of them guarantees indexing.
If you bought a placement, you usually don't have Search Console access to the publisher's site. URL Inspection only works for properties you own, so you can't run these checks yourself. The publisher can, and a short, specific request gets a faster and clearer answer than "why isn't it indexed?".
Request template: Could you inspect [article URL] in Search Console and share its indexing status, last crawl date, crawl and indexing permissions, and Google-selected canonical where available? If you have fixed an issue, please confirm the change and whether the live test now passes.
A hypothetical example: a publisher finds a noindex tag on your article and removes it, but Google's last crawl happened before the fix. The indexed result still shows "excluded by noindex", while the live test now passes. Comparing the two tells you the problem is solved and only a recrawl is missing. In that case, the right request is for the publisher to ask Google to index the URL, not to change anything else.
Before you buy, it also helps to check how a publisher handles this kind of question. Our guide on how to evaluate a link opportunity covers what to look at. Once a link is indexed, here is how to tell if your link building is working.
There is no fixed deadline. Google says crawling can take anywhere from a few days to a few weeks, and indexing does not always follow a crawl. Check the URL Inspection data rather than waiting for a set number of days.
No. A request asks Google to crawl the URL. Google says this does not guarantee the page will be included in its index quickly, or at all.
Not with URL Inspection or an indexing request, as both only work for properties you have verified. Ask the publisher to run the checks and share the results, using the template above.
A live article that isn't indexed is a question to diagnose, not a verdict. Check the exact URL, separate stored data from the live test, work through crawl access, indexing rules, canonical and last crawl, and give the publisher a precise request.
Follow Zemvoq on LinkedIn for practical SEO and link-building checks.