Social Icons

Pages

Showing posts with label PageID. Show all posts
Showing posts with label PageID. Show all posts

Friday, 23 August 2013

Recovering A Deleted Page Or Post, Chapter 3

We've been advising anxious blog owners, for some time, how to recover deleted pages and posts.

The easiest solution, in the long run, is to recover the PageID / PostID, and re publish the deleted page / post.

Unfortunately, all deleted pages and posts can't be edited and re published. With new posts, un indexed by the search engines, you won't be able to find the post in cache - and you'll never determine the PostID. This will be a frequent problem with deleted pages - as static pages generally won't get indexed by the search engines - nor will they ever be included in the blog posts feed.

In some cases, even when you know the PageID or PostID, the page editor / post editor may simply reject your attempt to re edit - and give you another bX code.

Even so, all is not lost. You may have to rebuild the page or post - but you can generally keep the URL, of the deleted page or post, operational. Just plan the rebuilding process.

In cases where a deleted page or post can't be simply re published, you can publish a replacement page or post - and redirect both your readers, and the search engines, from the URL of the deleted page / post, to the replacement page or post.

To minimise loss of reader and search engine reputation, you'll want to publish a replacement page / post as soon as possible after the old page / post is mistakenly deleted. With replacement posts published in the same month as the original - and with all pages - this can cause the well known ugly URL suffix, to prevent a duplicate URL.

When you publish a replacement page or post, you have one chance to get the title and URL right - and prevent the ugly URL suffix. The one chance ends, when you hit the "Publish" button.

With a deleted post, you can use the Custom Permalink option ("Permalink", under "Post settings", in the post editor window) to make the published URL slightly different from the default. Alternately, you'll need to deliberately choose a slightly different Title, for the replacement post.

When you publish a replacement page, you won't have a "Custom Permalink" option. Your only option, in this case, is to choose a slightly different Title, for the replacement Page.

Static page URLs do not contain the year and month of publishing, so you'll need to use a different Title for every replacement page - even if you publish the replacement in a later month, or even a later year. Since static pages are generally not as widely publicised as posts, the different title should still be preferable to the alternative - the ugly page URL suffix.

Just choose the title and URL carefully, before you hit "Publish", to prevent long term embarrassment. And having published the replacement, setup a Custom Redirect, to keep the URL of the deleted page or post operational.

>> Top

Sunday, 17 March 2013

Recovering A Deleted Page Or Post, Chapter 2

Blog owners have been deleting their pages and posts, then changing their minds later, since Blogger started providing the ability to delete pages and posts.

We've been advising anxious blog owners, for some time, how to recover deleted pages and posts. The easiest solution, in the long run, is to recover the PageID / PostID, and re publish the deleted page / post.

When the deleted page or post cannot be re published, the next option is to re build the page / post, possibly using feed cache.
Using this technique, you'll have to reformat the post content, as feed content is formatted relatively simply. When you publish the post, it will publish as a new post, with a new URL - so any external references to the missing post URL will still be broken.
Thanks to the recently offered Custom Redirects option, though, we can make this latter choice slightly less undesirable.

When a deleted page or post has to be rebuilt from the beginning, the classic prognosis was not good.
  1. The content is retrieved or rewritten, then re formatted.
  2. The page / post is re published, but under a new URL.
  3. The readers, and the search engines, adjust to the new URL being used.
For many blog owners, issue #3 is the cruelest blow - as the blog suffers reputation loss, from readers and search engines seeing
404 Not Found
for the deleted page / post.

Given enough determination and time, the blog owner can get through issues #1 and #2 - but issue #3 is the gift that just keeps on giving. Using Custom Redirects, though, that does not have to be the case.

It's a simple solution - and your readers and the search engines don't have to do anything unusual.
  1. Rebuild the page / post, using a carefully chosen Title / URL.
  2. Add a Custom Redirect.
    • From: The deleted (previously published) URL.
    • To: The new (re published) URL.
  3. The readers, and the search engines can view the re built page / post contents using the old URL - and update their record of the URL, as convenient to them, to point to the new URL. And the page / post never goes offline.
And you, the blog owner, can get back to work on new pages and posts.

>> Top