Pasted a Google, Apple News or Shortened Link and It Failed? How to Get the Real Article URL

When an article will not load in a paywall reader, the obvious guess is that the paywall won. Our own analytics for 10 to 13 October 2026 tell a different story: a large share of failed reads were not paywalls at all. They were wrapper links. The address pasted into the box was a Google share link, a Google News link, an Apple News link, a shortener, a Facebook or Outlook "safe link", or a doi.org link to a research paper, and the real article was hidden somewhere inside it, or not inside it at all. This post explains which of those links work, which cannot work, and how to get the publisher's address in each case.

What a wrapper link is

A wrapper link is an address that belongs to a service rather than a publisher. When you tap it in a browser, that service either redirects you to the real page or opens the story inside its own app. Some wrappers are transparent: anyone who follows the link ends up at the publisher's address. Others only work in a browser or a specific app, and the publisher's address is encoded, truncated or missing entirely. A reader that fetches pages from a server can only follow the first kind.

Links that work: shorteners and share.google

share.google links, t.co (X), bit.ly, trib.al and most other shorteners redirect normally, and Skip the Paywall follows them. On 13 October 2026 we pasted a share.google link to a Times (UK) health interview and the article loaded in full, 1,059 words, exactly as it would have from the direct link.

Facebook's l.facebook.com redirector, Instagram and Threads link wrappers, and Outlook safelinks (the safelinks.protection.outlook.com addresses that corporate email adds to every link) are also unwrapped automatically as of 13 October 2026. You can paste them as they are.

Tracking parameters such as utm_source, fbclid and gclid are harmless. The reader strips them before fetching, so there is no need to tidy a link by hand.

Links that often fail: google.com/url

A google.com/url link is a redirect that Google puts in front of search results and some shared links. It does carry the real address, in a parameter called url or q, so a complete one should work. The problem is that these links are long, and messaging apps cut them. The analytics show many pasted google.com/url addresses that contain nothing but an opi= parameter, which is the tail end of the link with the actual destination missing. There is nothing for the reader to fetch.

The fix: open the link in a browser first. Once the page has loaded, copy the publisher's address from the address bar and paste that instead.

Links that cannot work: news.google.com

news.google.com/read/... and news.google.com/rss/articles/... links are different. The article address is in there, but only in an encoded form that Google decodes when the link is opened in a browser. The reader cannot decode it, so a Google News link will always fail, whatever the publisher.

The fix: open the story from Google News so that it lands on the publisher's site, then copy the address from the address bar. In the Google News app, long-press the headline and choose the option that gives you the publisher's link rather than the Google News one.

Links that cannot work: apple.news

apple.news links point at Apple's app. The web page behind an apple.news address contains only the channel name, not the publisher's address, so there is nothing a server can follow. As of 13 October 2026 the reader recognises an apple.news link and explains this instead of showing a generic error.

The fix: in Apple News, open the story, use the share menu, and choose the option to open it in Safari or to copy the original link. That gives you the publisher's address, which you can paste into the reader as normal.

Research papers are a different job

doi.org, sciencedirect.com, link.springer.com, onlinelibrary.wiley.com, tandfonline.com and similar addresses are research papers, not news articles. They sit behind a different kind of paywall and need a different kind of tool. The reader now points those links to Research Papers Free, a sister site built for papers.

Which link to copy

A quick checklist before you paste:

• Does the address start with the publisher's own domain? If so, paste it. Tracking parameters do not matter.
• Is it a shortener or a share.google link? Paste it. The reader will follow the redirect.
• Is it a Facebook, Instagram, Threads or Outlook safe link? Paste it. The reader unwraps it.
• Is it a google.com/url link? Open it in a browser, then copy the address bar.
• Is it a news.google.com link? Open the story, then copy the publisher's address from the address bar.
• Is it an apple.news link? Share from Apple News and choose open in Safari or copy the original link.
• Is it a doi.org or journal link? Use Research Papers Free instead.

On a phone, the iPhone and Android shortcut sends the page you are already looking at, which means you are always sending the publisher's address rather than a wrapper. The bookmarklet does the same on a desktop.

If the real link still fails

Once you have the publisher's address and it still does not load, you are looking at an actual paywall or bot-protection problem rather than a link problem. The complete guide and troubleshooting post explains each error message, and the full list of sites shows which publishers work.

Our recommendation

Before assuming a paywall has beaten you, look at the address you pasted. If it does not start with the publisher's domain, get the real link first using the steps above. In our analytics that single habit would have turned a large share of failed reads into successful ones.