Skip to main content

Viewing Your Blog Content, In Text Only

One of the most useful skills to have, when diagnosing a problem with your blog, is looking at the page source code.

Every browser has this alternative, called "Page Source" or "Source", and generally accessed from the "View" menu. I'll instruct you to View - Page Source for such basic tasks asSometimes, even this basic task is impossible.

If a blog is hijacked, maybe because of broken / malicious third party code, you're going to need to examine the source code.

In some cases, you may not be able to see anything useful, because the blog content is immediately redirected, outside your blog. Fortunately, that's not an insurmountable problem.

If you are viewing a blog in your browser, use "View - Source" or equivalent.

It may not always be convenient, possible, and safe, to view a blog in your browser. When it's dangerous, inconvenient, or impossible to view the blog in your browser, use an HTTP text proxy.

Use View - Source

Every browser, on the Internet, lets you view the source code, for the page currently being viewed. Depending upon the browser, source code listings are available in different ways.

For most browsers, you'll have a menu at the top. One of the menu entries should be "View" - and when you click on "View", the sub menu entries should include "Page Source" or "Source".

Besides the menu, try a key click combination. Chrome uses "Control - U".

Finally, most browsers provide a context menu, available from the "mouse" right click button. The context menu, when displayed, may also include "Page Source" or "Source".

Use A Text Proxy

There are many text proxies on the Internet, and it's good to have 2 or 3 available. The two that I use, right now, are Lingo4You HTTP Web-Sniffer and Rex Swain's HTTP Viewer. Neither is complicated to use.
  • For Lingo4You, you
    1. Paste or type the URL that interests you into the "HTTP(S)-URL:" box.
    2. Change nothing in the options.
    3. Hit Enter, or the Submit button.
    4. Watch while the screen is refreshed.
    5. Note that Web-Sniffer will display one page / redirection step, during the retrieval process. If a redirection is relevant, you'll see a clickable link in the "HTTP Response Header" section, above "Content".
    6. View blog content, in the "Content" box, at the bottom.
  • For Rex Swain, you
    1. Paste or type the URL that interests you into the "URL" box. Note that Rex Swain requires the "http://" prefix with the URL, and will not do "https".
    2. Change nothing in the options.
    3. Hit Enter, or the Submit button.
    4. Watch while the screen is refreshed.
    5. Note that Rex Swain will display the entire sequence encountered, during the retrieval process, including all redirections.
    6. View blog content, in the Content section at the bottom of the page.

With the blog content in text, you can do things like extract gadget editing URLs, to avoid having to load the blog or dashboard in emergency situations.

Occasionally the different capability of one proxy, such as those described above, may make a difference between solving a problem, and scratching your head. And sometimes, one proxy may go offline for a while. So having multiple choices never hurts.

If you know of any similar products (free is best), and wish to share, I will gladly add any useful tools to this list.

Know The Alternatives

Know, and understand, the alternatives. Sometimes, choosing the right one will be more convenient - other times, more safe. Understand the differences.


Dale said…
Hello, I have the bloggroll problem. I delieted all of my known widgets and the problem is still there. I took a look at my template and this is what I found.

Now these are the heading within this includable:
None of these includables did I allow into my template. I would like to errase these to see if this will fix the problem.
Input please, Thank you. Dale
Chuck said…

The problem gadget, HTML3, is right there, in your blog. Please try using my improved diagnostic instructions, and let me know which portion of the instructions need still more clarification.
Dale said…
Hey Chuck,
Thank you for the help. It took me some time to figure out how to erase the HTML 3, but I got it. My blog works fine now.
Haura Malina said…
I have tried remove some gadget through page element but still it redirect to

Help me please..... :(

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: