Recently there has been a spate of American news sites returning a page that says the content isn’t available to me since I’m in the UK / EU and, because I’m subject to some unspecified horror to do with the GDPR and cookies, the website is worried about me seeing it and hopes I might just go away.

About 90 per cent of the time this problem is rapidly solved by searching for and reading Google’s cache of the page. The appearance may be a little different but the text is usually there and perfectly readable. Here’s an example of how to do this.

Yesterday I wanted to read the awful story about a young black woman who died after it was assumed she’d not be able to pay for the ambulance service that she needed. Her mother had found her slumped in the bath after she’d collapsed with a suspected stroke. She’d given birth via C section a few days before.

Try this – it doesnt always work thoughThe next stage is to copy that address / URL (the wpbf.com bit next to the green padlock) – the quickest way to do that is to put the cursor into that address bar, it should automatically select the URL but if not Ctrl+A will do that. Then Ctrl+C to copy and open a new tab with your preferred search engine and paste (Ctrl+V) into the search bar and search [see also: handy keyboard shortcuts]

Ignore the top stories option. You might just about be able to make out a tiny little green arrowhead pointing downwards to the right of the green URL for this search result. That’s where Google hides the cache of its pages. Here’s a close-up.

Fig 3. Where to find cached copies of pages, if available

Clicking on the green arrow will bring up a menu saying ‘Cached’ and clicking on that usually, but not always, bring up the page you want – it did in this case too.

Fig 4. In this instance the cached copy was available and readable

The entire text is visible but for copyright reasons I’ll leave it at that. Here’s the link if you want to read it yourself, it’s a sobering read.

This is a very useful and more widely applicable trick
There are other cases (*cough*) where content isn’t shown to you, for all sorts of un-GDPR related reasons. It is nearly always worth checking the cached version first before either admitting defeat, asking a friend for a copy or reading a different newspaper’s story.

For the exceptionally patient
At the bottom of Fig 2 there’s a paragraph of text beneath the green URL and the green padlock. Google can nearly always read the page (whether there’s a cached version or not) even if you can’t. If you search for a phrase that appears there (put it in ” ” marks when searching) then Google will show that phrase in the search results, often in context which means it may show other bits of surrounding text. Frankly it takes ages but it may be possible (I’ve done it to uncover and reference a quote for work once) to work your way through very slowly and uncover a large portion or even the entirety of the otherwise hidden text.

Every tweet sent has its own web page with an address (URL) that will point to it. You can share this link in a tweet of your own, how the tweet appears will depend on what app or platform other readers are using.

On Echofon for iPhone the tweet will appear as your text plus a clickable link to the tweet but on desktop Twitter the system will convert the tweet’s link into a visible embedded tweet that shows up without having to click on the link or tweet to view it. I believe this is the same on Twitter for iPhone etc. It will also appear in the Notifications tab of the original tweet sender.

It’s important to be aware of this as people have previously used this technique to ‘sub-tweet’ (ie send a critical tweet about someone else’s tweet without that person being aware). Fortunately, or unfortunately, Twitter changed how such tweets were handled and this is now more easily discoverable. Previously they’d have had to search for tweets mentioning their username, eg by searching username or twitter.com/username).