← All posts

How to Index a Medium Article

How to Index a Medium Article

Publishing on Medium takes almost every technical decision out of your hands, which is both the appeal and the problem. There is no robots.txt to edit, no meta tag to add, no server header to set, and no sitemap of your own to submit. So the honest way to explain how to index a Medium article starts with a subtraction: most of the standard indexing advice does not apply here, because Medium owns the domain and you do not.

What is left is a short list: two editor settings that decide what Google can make of the page, a few discovery paths you can widen, and a verification problem that Medium’s ownership creates and cannot solve.

Why a story can sit unindexed on a strong domain

Medium is crawled often. A new story is usually discovered quickly, linked from your profile, from tag pages, and from any publication that accepted it. Discovery is rarely the bottleneck.

Indexing is a separate judgement. Google crawls a URL and then decides, on its own terms, whether the page belongs in the index. A domain with a long crawl history gets looked at sooner. It does not get its pages waved through. Each article is assessed as its own URL, which is why two stories posted on the same afternoon from the same profile can end up in different places. If you publish on Medium partly to borrow the domain’s standing, borrow the matching expectation too: you are buying earlier attention, not a decision.

Check the canonical tag before anything else

If the piece began life on your own site and you moved it across with Medium’s import tool, Medium adds a canonical link pointing back to the original URL. That is correct behaviour and usually what you want: Google consolidates duplicates onto the URL the canonical names, so the credit stays with your site. It also means the Medium copy is not competing to be indexed in its own right, and no amount of submitting will change that.

So decide which URL you want in the index, then make the article match. An imported story with a canonical pointing home is doing its job by staying out of the results. A story written natively in the Medium editor carries no such tag and stands alone. Muddling the two explains a fair share of stories that look neglected but are behaving exactly as configured, and it sits alongside the other quiet causes in six reasons Google declines to index a page that looks fine.

How to index a Medium article without Search Console

This is the constraint that separates Medium from a site you host. Search Console works on properties you can prove you own, so you cannot verify medium.com, cannot submit a sitemap for it, and cannot use URL Inspection to ask Google to recrawl one of your stories. The tools most indexing guides open with are simply closed, and no workaround gets around ownership.

The levers that remain are ordinary, and they are where the time goes:

  • Publish into a publication that fits the piece. A publication adds internal links and archive pages pointing at your article, which is more crawl surface than a lone profile provides.
  • Link it from a page you do own. One link from a site Google already crawls regularly is a more reliable path than waiting for Medium’s own surfaces to do the work.
  • Use tags that are actually used. Tags place the story on Medium’s topic pages, which are plain crawl paths like any other listing.
  • Give the page something to index. A story that mostly restates its own title has thin odds anywhere, and the platform does not compensate.

The two settings that change what Google sees

Marking a story member-only puts it behind Medium’s paywall, and what a crawler fetches then depends on how Medium implements that paywall rather than on what a signed-in member sees. Marking a story unlisted keeps it off your profile and off Medium’s topic pages, which removes most of the internal routes that would otherwise lead a crawler to it. Neither is a fault, and both are worth ruling out before you go hunting for one. If you want the article indexed as widely as it can be, publish it public and listed.

One more thing to check before assuming a problem: if you renamed the story after publishing, the readable part of the address changed while the trailing identifier stayed put. Make sure the URL you are checking is the URL you have been sharing.

Submitting from outside, and verifying afterwards

With the Search Console route closed, the remaining option is a tool that submits from outside without asking you to prove ownership. AIndexify takes a pasted URL or a CSV, needs no Search Console connection, no ownership proof, and no tag anywhere (there is nowhere on Medium to put one), then checks the URL against live Google results on a fixed schedule. It reports submitted and indexed as two separate events, which matters more than usual here: submitting asks Google to look, it does not oblige Google to keep what it finds. That distinction is the whole subject of submitted is not indexed. If the URL returns a noindex, a 404, or a robots block, the preflight catches it, marks the URL Couldn’t check, and refunds the credit rather than billing a check that cannot succeed.

Verification is the step people skip on Medium, precisely because the usual instruments are missing. It is easy to publish, watch the story collect reads, and assume Google has it. Read counts come from Medium’s own distribution and say nothing about the index. For how discovery, crawling, and indexing fit together on any platform, the ultimate guide to Google indexing covers the full sequence.

Medium gives you a fast start and takes the instruments away. Submit your URLs and see, with dates, which of your stories Google has actually kept.

Sources