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

Deleted Comments Cannot Be Recovered

Blogger blog owners, who are accustomed to recovering deleted files on a personal computer, will find Blogger Comments to lack useful protection.

If you accidentally delete a file on your personal computer, no worry - just look in the Trash Can, find the file in question, and recover the file. Just do this before you empty the Trash Can.

Comments, published on our blogs, cannot be recovered once deleted.

I deleted a comment - but now realise that I acted in haste. How do I recover the comment that I deleted?

To this person, there is no useful answer.

Whether you moderate comments before or after they are published - and whether you moderate using the dashboard Comments wizard, or your email Inbox - once you click on "Delete" (and possibly hit "Yes"), the comments in question are gone. There is no Trash Can for deleted comments.

Some blog owners will retrieve the deleted content (possibly, from email), and manually re publish the content, when possible. Unfortunately, that will produce a comment with (possibly) the deleted text - but no link to the originator of the comment deleted. If the text content of the comment is the relevant detail to you, as the blog owner, you may do this - but the republished comment won't be the same.

Delete comments with care. Once you delete a comment, you won't get it back.

>> Top

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

Deleted / Locked Blogs Have Several Causes, And Various Resolutions

Many blog owners are occasionally confused, by the effects of several Blogger / Google security processes, when they are simply trying to login to Blogger and work on their blogs. We see the agony, daily, in Blogger Help Forum: Something Is Broken.

The side effects of the security processes are similar - and depending upon various owner specific details, can be easily confused for each other. The possibility of confusion requires careful initial analysis, when we are faced with an angry blog owner.

My blog was deleted, by Blogger. How could they do this? I do not publish spam!

This is a typical problem report, which can reflect any one of the processes, each requiring different action in the forums.

There are various Blogger / Google security / TOS enforcement processes, each of which will cause a Blogger account and / or blog to be unavailable for full access, at any time.

• DMCA Violation looks for copyright and similar violations.
• Hacking detection looks for automated attacks against our Blogger accounts and blogs.
• Malware detection looks for malicious code installed in our Blogger blogs.
• Porn classification looks for blogs with adult content, and with unacceptable advertisements (aka monetised porn).
• Spam blog classification looks for Blogger blogs which contain spammy material or use spammy techniques.
• Repeated offenses can have gradually increasing severity of action taken.
• Owner deletion or rename may be confused with spam classification.
• Team blog ownership will affect blogs owned in common, by that team.

Each different process has a different effect on the Blogger account and blogs owned - and requires different attention by the blog owners, by the forum helpers, and by Blogger Support and Google Security.

DMCA Violation

Accounts and blogs can be deleted, for progressive DMCA violations.

The DMCA violation process originated with complaints made by the major entertainment industry content enforcement organisations, citing theft of "intellectual property" which they control. In the USA, this would involve the "MPAA" (Motion Picture Association of America), and the "RIAA" (Recording Industry Association of America). I have been told that similar content enforcement organisations exist in other countries.

In more recent events, private citizens have been known to use the DMCA Violation complaint process, for miscellaneous copyright violation reporting.

DMCA Violations have a formal complaint and appeal process.

Hacking detection

Blogger / Google network monitors are constantly analysing account login activity, and looking for signs of brute force password hacking. When hacking activity is discovered, the Blogger account - and all blogs owned by the account - are deleted and locked, pending account verification by the owner, and blog integrity checking by Google Security.

The blog owner, after changing the account password, solving a CAPTCHA, and / or verifying account ownership by providing various personal details, is left waiting for the blogs owned by the account to be examined for signs of abuse by the hacker. Until the blog(s) are returned to online status, they appear in neither the "Deleted blogs" or "Locked blogs" dashboard lists. The owner, even when logged in to the right Blogger account, simply sees the dashboard advice

You are not an author on any blogs.

In this case, neither the blog owner nor the forum helpers can do anything useful, except wait, anxiously - possibly, with no notice provided. The blog being offline may not be immediately observed by the owner - and this may cause more confusion.

Malware detection

Blogger robotic processes are constantly checking the various blogs, looking for malicious blog accessories, components, and scripts. When a blog is subject to "Malware" classification, the blog will appear in one of two dashboard lists, in sequence.

1. Initially, the blog will appear in the "Deleted blogs" list. While the blog is in "Deleted" status, the blog owner will be able to do nothing, except request "Restore".
2. Once the owner has requested "Restore", the blog is undeleted, and placed into the "Locked blogs" list. While the blog is in "Locked" status, all authors can access the blog to remove malware - but the blog remains offline, to all viewers. Once all malware has been removed from the blog, the owner can "Request Unlock Review".

If the blog remains in "Locked" status for over 48 hours, the blog owner may report this in the forums, and may request a manual review. The forum helpers, and online viewers, will generally see the blog displayed as "TOS violation".

This blog is in violation of Blogger Terms of Service and is open to authors only

Adult Content / Porn Detection

Blogger will soon classify and delete blogs with "adult content", which host advertisements to commercial porn sites. Like spam classification, this will probably involve both false negatives and false positives.

Spam detection

Blogger robotic processes are constantly checking the various blogs, looking for signs of spam activity and content. When a blog is subject to "Spam" classification, the blog will be displayed in the "Deleted blogs" dashboard list. The owner can do nothing, except request "Restore".

If the blog remains in "Deleted" status for over 48 hours, the blog owner may report this in the forums, and may request a manual review. The forum helpers, and online viewers, will generally see the blog displayed as "Removed".

Blog has been removed
Sorry, the blog at xxxxxxx.blogspot.com has been removed. This address is not available for new blogs.

Repeated Offenses

We have recently noted that repeated TOS Violations, involving DMCA, Malware, Porn, and Spam, are being dealt with in increasing severity.

Owner deletion or rename

Mistakes made by the owner can be confused with Spam detection. When a blog is deleted by the owner, it will appear in the dashboard "Deleted blogs" list for up to 90 days. During the 90 days, the owner (or a team member, when applicable) may "Restore" the blog. After the 90 days expire, the blog will be removed from "Deleted blogs", and will be unrecoverable. Besides being unrecoverable, no other details have been determined.

If the blog is renamed (published under a different BlogSpot URL), the external symptom may be similar to deletion by the owner.

Blog has been removed

Sorry, the blog at myblog.blogspot.com has been removed. This address is not available for new blogs.

In this case, the blog will be listed in the dashboard "My blogs" list, under the right Title. The owner needs to setup a stub blog, pointing the readers to the new URL.

Team Ownership

Any blogs owned by a deleted / locked Blogger account may simply disappear from the dashboards of other team members. If the Blogger account is not restored / unlocked, the blogs owned by that account - including any team owned blogs - may remain deleted - and inaccessible to everybody.

The Confusion Accumulates

Because of anonymous blog ownership, loss of account control, team blog ownership, and use of inactive or non existent email addresses, any account / blog which is deleted or locked for hacking (actively / as a victim), malware, and / or spam may not be easily discovered or recovered by the owner. These issues cause further confusion and frustration.

These scenarios may appear, to the untrained eye, to be signs of fraudulent, malicious, and / or petty actions by Blogger - and are loudly claimed so by spammers with their own agenda. None of these accusations are true - the above processes simply represent Blogger and Google attempting, in the best possible way, to protect everybody against the various hacking, malware, porn, and spam attacks which are constantly in progress.

>> Top

Without The PostID, A Deleted Post Is Not Easily Recovered

If you delete a post (page) in your blog, it's a simple matter to recover the post - as long as you know the PostID. Unfortunately, once the post is gone, finding the post (page) id is not a simple matter - especially for those who would typically delete a page or post without planning. Blogger does not provide the PostID in any list, that we might save, periodically, to reference later.

The task of retrieving a deleted page or post is particularly frustrating, for owners of private blogs. Private blogs probably won't be cached, nor do they publish a blog feed - and without either a cache entry, or a feed reference, the PostID for a deleted post is not easily obtained.

Right now, once you delete a page or post, in a private blog, you're out of luck - unless you have cached the blog on your own computer. Retrieving from local cache is not an issue to be productively discussed in Blogger Support, as it is going to be as individual as your computer may be.

>> Top

Submitting A Court Order To Google

Periodically, we have discussions in Blogger Help Forum: Something Is Broken, about issues, that absolutely cannot be resolved in a forum problem discussion.

These issues will vary, by relationship to a given blog, as well as by nature of the offense perceived.

• Some blog owners have lost control of their Blogger account, and lack ability to recover control.
• Some people are offended by a Blogger blog, but an offense which may not constitute a Google TOS violation.
• Some people may believe that a Blogger blog name, in use by someone else, may reflect badly upon their hard earned business identity.
• Some people may be the survivor, in a relationship where the owner of a given blog is now deceased.

Some of these complaints may have been reported to Google, in an ongoing effort, for years.

We know that Google Legal has to take a conservative approach in evaluating the various complaints submitted to them, using the Google Content Removal process. Every complaint may involve a third party, who has equal rights that must be considered.

In cases where Google Legal must deny action, and generally will not respond to a submitted Content Removal form, the person making a complaint is advised to use the courts to verify his identity and / or legal relationship with the blog in question.

Anybody who does not receive appropriate response from Google Legal may hire a lawyer, start a lawsuit, and get a court order issued by a judge. A properly issued court order can be then submitted to Google using the Google Help: Submit a Court Order to Google form.

>> Top

Blog Owners Seeing bX-afpmyd When Trying To Un Delete Custom Domain Published Blogs

We're seeing a few reports this week, from blog owners who recently deleted their custom domain published blogs - who now lament their decision - and who are unable to un delete the blogs.

I can't "undelete" my blog, that used to be published as a custom domain URL. I received the following error code: bX-afpmyd.

This problem, like others, appears to have started when custom domain publishing was restored, last week.

Blogs deleted when a custom domain URL is in use have always been a challenge. Similar to the abandoned custom domains problem, they have resulted in yet another cause for the well known custom domain problem

Another blog ....

Now that Blogger is requiring verification of domain ownership, by adding ownership certification using a new "CNAME", it's likely that either lack of the new "CNAME", or broken blog / domain pointers, are going to be a problem when un deleting blogs formerly published to custom domains.

If you are unable to un delete your previously deleted custom domain published blog - and you are otherwise able to restore the blog in question - you, like other blog owners trying to make changes to their custom domain published blog, will need to use the Publishing wizard, and the "settings instructions", and add a unique domain ownership certificate to your non BlogSpot domain. Then, if able to un delete the blog, you'll need to re publish the blog to the domain.

>> Top

A Team Blog With No Administrators Is Given To The Authors, For Their Control

We have known, for a while, that every Blogger blog has to have at least one administrator.

That rule is enforced by the Permissions wizard, which gives any administrator the choice to demote or remove any administrator, from the Permissions list - but only when there is at least one other administrator in the list.

When the Permissions list is displayed, if there are at least two members with administrative authority, each administrator entry, in the list, has a link to demote or remove that member. If there is only one member with administrative authority, there is no such link - and that member can be neither demoted or removed from the list.

As long as only the Permissions wizard is used, to demote or remove administrators, this article would be meaningless (see the above link). But, there is another way for administrators to be removed - and this occasionally leaves blogs with no administrator.

If the only way to lose an administrator (or member) from a blog was by using the Permissions list to demote or remove, then the Permissions list setup, as described above, would be sufficient.

Unfortunately, the Blogger - and Google - account deletion processes don't consider the member lists for the blogs owned by the account. When a Blogger account is deleted, the fate of the blogs owned, by that account, has to be decided later.

Any blogs which have only one member (the owner) are either frozen or deleted - as with only one owner, there is no need to keep those blogs. Any blogs with more than one member simply lose that one member. But what if a blog has more than one member, but only one administrator - and that one administrator takes a hike?

With a team blog with one administrator, and one or more authors, losing the one administrator would leave a blog that was being published (by the authors), but could not be managed (because there was no administrator). This would, in the past, lead to panic in the forum.

The administrator for my blog deleted his Blogger account - and now my blog has no administrator! What do we do now?

With no administrator existing, Blogger Support would be summoned, and would have to determine whether a blog:

• Had no administrators.
• Had at least one author.
• Was being requested by a person who had a legitimate need to request control (a former administrator, or a current author).

Failure to ensure that each condition was being properly met could, with the right problem report, allow a hijacker to improperly assume control of someone's blog - with only Blogger Support to blame for enabling the hijacking.

To allow control recovery without needless delay, and avoid the need for endless detail in verifying any such panicky report, Blogger Engineering made a simple procedural change. The "Forgot your username or password?" wizard, when control recovery is requested for a blog with no administrator, simply sends the appropriate access tokens (aka "login instructions") to all blog authors - as long as the membership list is well maintained.

Any blog authors, able to receive the login instructions, then become de facto administrators - and can jointly determine the fate of the blog. The control recovery process can be automated, and the risk of possible hijacking of actively owned (administered) blogs is reduced. This simply requires that at least one blog author uses a Blogger account based on an active and genuine email address - and if necessary, can search persistently for the email sent.

When this reset process is done, each author of the blog initially has the same power as each of the other authors. Blogger leaves it to all authors to act honourably - and to politely choose one or more authors to be administrators. As long as the author submitting the reset process is able to locate the email message in his Inbox immediately, he can make himself the sole administrator - if he decides.

If one of the authors has problem locating the email, it's possible that the other newly appointed administrators could unwisely hijack control of the blog. If this happens, it will be up to the authors to jointly establish order. Blogger Support will not be involved in any conflict.

The more authors a given blog may have, the greater the chance that one author, receiving the email message, may act dishonourably, and hijack the blog. In cases where there are a large number of authors (precise number not known, right now), Blogger will defer to the author requesting the reset.

In this case, the author requesting the account reset can enter his email address, that is used by his Blogger account, to have the password reset email sent directly to him.

>> Top

Having A Blogger Blog Removed Or Restored, After Death Of The Blog Owner - The Next Chapter

The question of disposition of blogs, left behind by deceased blog owners, comes up in Blogger Help Forum: How Do I?, from time to time.

As Blogger blogs - and similar Google products - become mature, and as more people who publish Blogger blogs become susceptible to old age and death, this problem will become more critical. As recently as 2010, in order to assume control (or request deletion) of such a blog, Blogger required only a faxed copy of the death certificate.

We are now seeing that the death certificate is only one part of a formal procedure, which Blogger / Google now uses, in the dual role of

• Compassion, in allowing a friend or loved one to appropriately assume control of blogs left behind.
• Due Diligence, in preventing fraudulent claims by people who have no legal or moral right to assume control of blogs.

Both roles are righteous, and are needed to help Google reduce hijacking of active Blogger blogs.

As part of an improved procedure for disposition of Blogger blogs left behind by deceased owners, Blogger now uses GMail Help: Accessing a deceased person's mail as guidelines. The new guidelines

1. Use a two part process - a preliminary review, followed by a formal court documented process.
2. Include a dedicated facsimile transmission / postal mail address.
3. Include additional requirements, which formally identify the relationship of the person requesting control of the blog in question, to the deceased.

The preliminary review specifies a facsimile transmission / postal mail address:

Google Inc.
Gmail User Support - Decedents’ Accounts
c/o Google Custodian of Records
1600 Amphitheatre Parkway
Mountain View, CA 94043
Fax: 650-644-0358

and a formal list of material required, for Part 1 - preliminary review.

1. Your full name.
2. Your physical mailing address.
3. Your email address.
4. A photocopy of your government-issued ID or driver’s license.
5. The Gmail address of the deceased user.
6. The death certificate of the deceased user. If the document is not in English, please provide a certified English translation prepared by a competent translator and notarized.
7. The following information from an email message that you have received at your email address, from the Gmail address in question:
   • The full header from the email message. See instructions on how to find headers in Gmail and other webmail email providers. Copy everything from 'Delivered-To:' through the 'References:' line
   • The entire content of the message

When specified by Blogger Support, we were instructed to substitute the blog URL, for the Gmail address (as #5). No addendum referencing the email message (as #7) was provided.

The instructions for Part 2 are not as well defined, as for Part 1.

Part 2 will require you to get additional legal process including an order from a U.S. court and/or submitting additional materials. Please note that submitting these materials will not guarantee that we will be able to provide Gmail content so we recommend not embarking on Part 2 until you hear back from us regarding Part 1.

These requirements may seem onerous to the less observant. Actually, by formalising the process, this should reduce the number of fraudulent claims, and make it easier for Google personnel to legitimately process claims, while exercising both compassion and due diligence.

>> Top

Blog Control And URL Availability Hacking - Four Sides Of The Same Story

Occasionally, in Blogger Help Forum: How Do I?, we see various queries about our blogs, and how to gain or regain control.

• How do I get a blog, which is attacking me (impersonating me, insulting me, publishing my secrets), removed from Blogger?
• How do I claim a dormant URL?
• How do I recover control of my blog?
• My blog is now under somebody else's control! How do I get my blog back?

In some cases, all of these queries are simply one more attempt to gain control of a blog, or a URL. As we gain experience in reading between the lines in Blogger Help Forum, and as Blogger Support gains experience in researching blog histories, we can start to see patterns, and signs of multiple attempts to assume control of the blog - or the URL - in question.

Many blog or URL hacking attempts start quite innocently. Two of the more common ones are quite naive, and completely separate, tales.

• Some people want to recover control of their blog, after having forgotten the username / password.
• Other people want to start a blog - but find that the desired URL is not available.

Some people, denied recovery of the blog, because they can't prove ownership, will try another tactic.

I'll tell them that the blog was stolen from me. Surely if they think the blog was hacked, I can get it back, since I used to be the owner!

People trying to gain control of a dormant blog will likewise use their imagination.

If I get the blog deleted as spam, I can grab the URL. Surely a Dormant blog is just another type of Spam, in Blogger!

Unfortunately, these techniques have been used, already - and have resulted in still other tales of anguish.

It requires the wisdom of Solomon - and the patient persistence of Gil Grissom - to sort through the problems reports. Claims

I just graduated from college, and I can't use my email address to recover the password!

and

I just woke up from a 7 year coma, to find my family blog under control of a hacker!

and let us not overlook

My friend just died. Can I please have control of the blog, so I can put a notice to all of his friends, on the blog?

and

I never updated my Blogger only account to a Blogger / Google account - and I never got any email, warning me of the impending change!

All of these tales have enormous human interest - and seem to justify mercy for the plaintive requests.

Unfortunately, these stories - and others like them - are not always what they seem. What we sometimes see are the other side of the story.

• Attempts to steal control of an active blog.
• Attempts to gain control of the URL which would be perfect for their new blog, if only the URL was available.
• Attempts to probe and reveal the identity of a blog owner, who is guaranteed anonymous blog ownership, by Blogger policy.

So, if you beg and plead for attention

None of these tools help me, in the least. Can I please speak to a live human, so I can explain my special need?

Please, do not be surprised to be directed to read about why Blogger Help is the only contact, and why you absolutely must prove ownership of the blog, before being given control. And even the ultimate insult, you must provide a copy of the death certificate plus get a court order, as you grieve for the loss of your friend or loved one.

The bottom line here is that, if you intend to publish a Blogger blog, it is your responsibility - and only your responsibility - to maintain control of your blog. You are an adult (or are presumed to be one) - and you have responsibilities, as an adult.

>> Top

Don't Delete Your Post (Or Page), To Rebuild It

Many people have a yearly ritual, called "spring cleaning", where the entire house gets a complete cleaning, from top to bottom. When one does spring cleaning, one does not tear the house down, however - one only cleans what is there.

Some blog owners seem to think that "spring cleaning" of a post starts with tearing the post down, as in deleting it and starting anew. We get an occasional query, from a perplexed blog owner, in Blogger Help Forum: How Do I?.

I rewrote a bunch of posts, and now all of the URLs have weird numbers at the end. How do I clean up the URLs?

and the only way to clean up the URLs is to start over, and re publish the original posts, with the non suffixed URLs.

When you delete a post (page) from your blog, all that you do is remove the post (page) from visibility. The post (page) is removed from

• The Posts (Pages) list.
• The published blog.

The post (page) is not removed from

• The blog feed.
• The blog post (page) database.

If you delete a post, then re publish a new post with that same title, during the same month as it was originally published, you have two posts with potentially the same URL. To prevent that happening, Blogger adds a suffix onto the re published post.

Pages are subject to the same duplication prevention, with one difference. You can have the same post URL, in two different months - but a page URL is unique for eternity.

I published a post "Don't Delete Your Post, To Rebuild It" this month.

http://blogging.nitecruzr.net/2012/06/dont-delete-your-post-to-rebuild-it.html

I can publish a second post "Don't Delete Your Post, To Rebuild It" next month.

http://blogging.nitecruzr.net/2012/07/dont-delete-your-post-to-rebuild-it.html

But I can only publish one page, for eternity.

http://blogging.nitecruzr.net/p/dont-delete-your-post-to-rebuild-it.html

If you don't want a post (page) with a suffixed URL, you must start over.

1. Hope that the blog is public, and the post has been indexed by a search engine.
2. Un delete the original post, using the BlogID and PostID.

Finally, you have to do what you should have done, in the beginning.

1. Clean out the original post, from the inside.
2. Re publish the original post.

That is the only way to do "spring cleaning" on the posts, in your blog.

>> Top