Friday, May 31, 2013

When Using Template "Edit HTML", The Edit Window Remains Blank

Since Blogger released their improved Template Editor, blog owners have been reporting a new, transient problem.
I click on "Edit HTML", and the editing display opens - but the HTML window remains blank.

Generally, you may wait a few seconds, and the HTML window will fill with the content. With enough patience, you'll see the content arrive - eventually.

Unfortunately, waiting won't always provide a solution.

Sometimes, you see the Template Editor display open, with a blank HTML window - and you wait patiently, with no result.

With the Template Editor display (common to every blog, and requiring no security) - and the Template HTML (unique to every blog, and requiring security) - coming from different servers - there's always the possibility that a dropped connection, from the Template HTML server, may cause the browser to time out.

In many cases, this will be a transient error. All that you need to do is to refresh the display.
  • Try a browser refresh. F5, or maybe Shift - F5, forces a refresh, in most browsers.
  • Restart the Template Editor. Click on Template, then "Edit HTML", again.
  • In extreme cases, clear cache, cookies, and authenticated sessions (since this is secure content, you'll need a new authenticated session) - then restart the browser, and start over.

If the lost connection is not transient, your Internet service may be part of the problem. If a simple refresh does not solve the problem for you, you may want to look at the MTU setting, on your computer.

An overly ambitious Maximum MTU setting could cause a chronic or persistent dropped connection, with the Template HTML server. Lowering the Max MTU setting could resolve this symptom.

>> Top

Wednesday, May 29, 2013

The Google Apps "bloggeradmin" Password Reset May Be Broken, For Some Domains

We've been seeing reports from some frustrated blog owners, about problems with the limited access Google Apps accounts.
I've reset my password numerous times and it still doesn't work.

Even given the recently provided "bloggeradmin" username, and the standard Google account reset process, some blog owners still cannot access Google Apps to manage their Blogger custom domain published blogs.

We do have one bit of hope. One such problem report, recently forwarded to Google Apps Support, was noted by a Google Apps Engineer with the advice
We identified a recent change which may have affected the password reset flow for some users. We expect it to either be fixed or rolled out shortly.

So, there is some hope for a few unhappy new domain owners. It's possible that this problem has been resolved, with Google Apps now using the new comprehensive Google login screen.

>> Top

Thursday, May 23, 2013

Abuse Reporting Is Not For Deleting Your Lost Blog

Sometimes, people lose control of their blog, with no ability to regain control - and simply want the blog deleted.
How do I have Blogger delete the blog, for me, since I can't prove ownership?

When advised that Blogger does not delete blogs on behalf of former owners, the next thought by the former owner is to have the blog deleted as abuse.
What category of Abuse should I use, to have a previously owned blog, deleted?

While not intentionally fraudulent, this approach is still misuse of the Abuse Reporting process.

The Abuse Reporting process is properly used to report blogs owned by another party, for TOS Violations.

Abuse categories are pretty complete, and specific.

Blogger currently provides the Blogger Help: Report inappropriate content form, which has specific categories of abuse.
  • Someone is copying my content or other legal concerns
  • Promotion of regulated goods and services
  • Hate speech, violent, or crude content
  • Harassment or bullying
  • Child safety, nudity, or adult content
  • Someone is posting my private information, or explicit content of me without my consent
  • Someone is pretending to be me
  • Someone is pretending to be a company or organization
  • Spam
  • Phishing
  • Malware
All of those categories refer to content published by another person. Nothing there is for reporting a blog previously owned, with control lost by negligence.




"Lost control of blog" is not abuse, it's negligence.

Whatever the loss of control, it's yours to correct.
  • Corporate blog, control lost.
  • Personal blog, control lost.
  • Team blog, control stolen.
None of these scenarios warrant abuse / TOS violation reports.

Misuse of DMCA violation process has financial and legal penalties.

Note a very specific warning, about misuse of the DMCA Violation complaint.
Please note that you will be liable for damages (including costs and attorneys' fees) if you materially misrepresent that a product or activity is infringing your copyrights. Indeed, in a recent case (please see http://www.onlinepolicy.org/action/legpolicy/opg_v_diebold/ for more information), a company that sent an infringement notification seeking removal of online materials that were protected by the fair use doctrine was ordered to pay such costs and attorneys fees. The company agreed to pay over $100,000. Accordingly, if you are not sure whether material available online infringes your copyright, we suggest that you first contact an attorney.

You need to accept responsibility - and not abuse the abuse mitigation process.

If your company publishes a blog, you are responsible for retaining control of the blog, as with any corporate asset. If you lose control of a corporate asset, you don't contact the vendor, and demand that they delete the asset that you lost. Your problem is with the current owner - whether it's a civil or criminal issue, it's not the responsibility of the vendor to correct an ownership problem.

If the blog was personally yours, and you forgot the account name and / or password, it's your responsibility to regain control.

If the blog was under team ownership, and another team member stole the blog, your problem is with the former team member. If the team member was (righteously or spuriously) classified as a non repentant spammer, you may have to get the blog reviewed, to regain control.

Improper abuse reports are not useful.

Bogus abuse reports accomplish nothing. Blogger Policy Review team members verify abuse reports, as submitted, in an ongoing effort to avoid falsely accusing righteous blog owners of publishing abusive content.

When you misuse the abuse reporting process, as you fraudulently try to get your non abusive blog deleted, all that you are doing is delaying a righteous policy review. Somebody else has to wait, yet one more day, for their non abusive blog to be restored - or to have a genuinely abusive blog deleted.

Since the spam filters are heuristic (learn as they go), your fraudulent spam report, if successful, may cause an improper filter update. Somebody else, righteously publishing a blog similar to yours, may be falsely accused - and may suffer a side effect of bogus spam classification.

Your final recourse is legal - and requires financial involvement.

If you believe that you can prove your right to control (or delete) the blog, you may hire a lawyer, and have a judge certify your identity. None of these cases can be resolved, using abuse / TOS violation reporting.

Just please, don't misuse the "Report inappropriate content" form!

Wednesday, May 22, 2013

The "Create a new blog" Wizard Is Not Prescient

We're seeing some odd problem reports in Blogger Help Forum: Something Is Broken, about blog creation.
I entered just the first letter of the name which I wanted, and I immediately saw
Sorry, this blog address is not available.
How am I supposed to create a blog, if all the names are taken?

What intrigues me here is not that people see
Sorry, this blog address is not available.
It's that people don't ask the next question.
How did it know what name I was typing, before I finished?

How do you explain that you have to type the entire name, and have that name checked, before giving up, disappointed?

Maybe the "Create a new blog" wizard is too good, for its own good.

Too much transparency actually makes it harder, for some people, to use it properly. Having the name checked for availability, as typed, one character at a time, may be a bit excessive.

Had I been creating this blog, long ago, as "bloggerstatusforreal.blogspot.com", I would have typed "bloggerstatusforreal" - and the "Create a new blog" would have checked, one by one
  • b
  • bl
  • blo
  • blog
  • blogg
  • blogge
  • blogger
  • bloggers
  • bloggerst
  • bloggersta
  • bloggerstat
  • bloggerstatu
  • bloggerstatus
  • bloggerstatusf
  • bloggerstatusfo
  • bloggerstatusfor
  • bloggerstatusforr
  • bloggerstatusforre
  • bloggerstatusforrea
  • bloggerstatusforreal

And I will bet good money, that I would have seen
Sorry, this blog address is not available.
during much of the typing.
  • b Sorry, this blog address is not available.
  • bl Sorry, this blog address is not available.
  • blo Sorry, this blog address is not available.
  • blog Sorry, this blog address is not available.
  • blogg Sorry, this blog address is not available.
  • blogge Sorry, this blog address is not available.
  • blogger Sorry, this blog address is not available.
  • bloggers Sorry, this blog address is not available.
  • bloggerst Sorry, this blog address is not available.
  • bloggersta Sorry, this blog address is not available.
  • bloggerstat Sorry, this blog address is not available.
  • bloggerstatu Sorry, this blog address is not available.
  • bloggerstatus Sorry, this blog address is not available.
  • bloggerstatusf
  • bloggerstatusfo
  • bloggerstatusfor
  • bloggerstatusforr
  • bloggerstatusforre
  • bloggerstatusforrea
  • bloggerstatusforreal
Since I created this blog, long ago, as an imitation of "bloggerstatus.blogspot.com", obviously "bloggerstatus" was taken. Most likely, the shorter names were likewise taken.

Then again, even if "bloggerstatus" was taken, that does not say, for sure, that "bloggerstatu" was. Or "bloggerstat".
  • b Sorry, this blog address is not available.
  • bl Sorry, this blog address is not available.
  • blo Sorry, this blog address is not available.
  • blog Sorry, this blog address is not available.
  • blogg Sorry, this blog address is not available.
  • blogge Sorry, this blog address is not available.
  • blogger Sorry, this blog address is not available.
  • bloggers Sorry, this blog address is not available.
  • bloggerst Sorry, this blog address is not available.
  • bloggersta Sorry, this blog address is not available.
  • bloggerstat Sorry, this blog address is not available.
  • bloggerstatu This blog address is available.
  • bloggerstatus Sorry, this blog address is not available.
  • bloggerstatusf This blog address is available.
  • bloggerstatusfo This blog address is available.
  • bloggerstatusfor This blog address is available.
  • bloggerstatusforr This blog address is available.
  • bloggerstatusforre This blog address is available.
  • bloggerstatusforrea Sorry, this blog address is not available.
  • bloggerstatusforreal Sorry, this blog address is not available.
Yes, I actually checked, one character at a time - and that's what I saw.

The bottom line here is that you have to type - and check - availability, one character at a time. And, you have to be persistent.

What would have happened, if I had given up, immediately.
  • b Sorry, this blog address is not available.
Dammit, all the names are taken!!

Well, you would not be reading "bloggerstatusforreal.blogspot.com" now, would you?

>> Top

Saturday, May 18, 2013

Confusion About Referer Spam Can Have Unexpected Consequences

As referer spam continues to be reported in Blogger Help Forum: Something Is Broken, we see occasional signs of confusion.

Some blog owners, knowing how to use WhoIs lookups and similar online utilities, to their advantage, are looking up the referer spam targets - and are reporting the targets to their registrars and hosts. What these blog owners may not realise is that not all apparent "customers" of referer spam "services" may have actually contracted to be featured in the services.

In October - November 2011, this blog was featured in one wave of referer spam.

Somewhere, buried deep in my comment moderation queue for this blog, may be some odd comments
Chuck, I clicked on a link in my Stats log, and got this blog. Your blog does not link to my blog - so why do my Stats displays link here?

When I saw one such comment, I thought that it was just some spammer, messing with me - as many do (which is why I moderate comments, aggressively). As more such remarks appeared, both here and in Blogger Help Forum, I realised that what I had idly expected, long ago, had actually come to pass.

I've been using this blog, since I started it, as a weapon against spamming activity in general. In February 2011, I started using it as a weapon against referer spam. I did both knowing well that if I was ever seriously effective in my fight, the guys who I became effective against would eventually attack me.

In October 2011, I realised that my dream had become true. I was honoured by the providers of referer spam, as someone worthy of their attention. In spam fighter parlance, I was the victim of a "Joe Job".

Just as surely as I, personally, was a Joe Job victim, I know that other honest and righteous blog and website owners are similarly being attacked by referer spam, in other Joe Jobs. I know that I am not the only fighter of spam, worthy of the attention of the spammers.

Once we understand that not all blogs or websites featured in referer spam activity may be actual intentional customers of referer spammers, we have to realise that unfocused reporting of blogs and websites, mentioned in referer spam, will actually play right into the hands of the referer spammers.

What the referer spammers are doing, in their Joe Jobs, is also called a "Smurf Attack". The spammers are hoping that thousands of angry Blogger blog owners will report the blogs and websites, featured in the spam, as spam customers. This will cause the immediate recipients of the Smurfing, the registrars and Internet Service Providers, to discontinue service to the reported blogs and websites. In 2011, with such reporting taken seriously, this blog might have been damaged.

Hopefully, most ISPs and registrars know of Joe Jobs and Smurf Attacks - and know how to verify the nature of any individual service being reported for spamming. However, that's simply a complication which can have other effects.

The bottom line is that anybody seeing the referer spam, in their Stats logs, has to understand that not all blogs and websites should be reported for spamming. When you report all referer spam, indiscriminately, you are simply working for the spammers.

Please, don't work for the spammers. The existence of this blog (and other, much more significant blogs and websites) may depend upon your discretion.

>> Top

Friday, May 17, 2013

Referer Spam Is Noticed More, By Newer Blog Owners

One of the details of referer spam, that intrigued me for a time, involved who was reporting the spam.

Most - but not all - referer spam is reported by newbie owners. People who just setup a blog, and are anxiously waiting for their first readers outside their own country, are suddenly astounded
Wow, thousands of people are reading my blog - from China and Russia! I am an international celebrity, in my first week!!

The euphoria quickly vanishes, when told in the forums
Nobody is actually viewing your blog from these sites - and nobody knows about these links but you, since only you can see your Stats logs.

The general response to the cold water, dashed in their faces, is generally acceptance

Thank you for the prompt and informative reply - I'm very relieved to learn that the site is not actually linking to my blog.

The latter is the general response - but not the only response. Nobody should be surprised at that, as not everybody is the same. What is surprising, though, is who is not so accepting of my advice.

Of the people who do not seem to appreciate my advice - that the owner of the new blog is not an immediate international celebrity - not all of them are actual first time blog owners.

Too many long time blog owners do not understand referer spam.

Many blog owners, who scorn my advice, turn out to be long time blog owners.

You are an idiot! I have other blogs, which I've been publishing for years - and none of them get this crap! How dare you tell me that this traffic is not targeting my new blog, intentionally?

Why would people who have published other blogs not see the spam traffic, in their other blogs? Particularly in other blogs that are well known, by the world, in general? And why would experienced blog owners not know of - or even believe - my advice?

The principle of Occam's Razor tells us to look for a simple explanation, to the questions.

Instead of concluding that so many experienced blog owners are morons - or do not check their Stats logs like everybody else - or wondering if referer spammers carefully tune their spammy activities to only attack new blogs - look for the simple explanation. Every blog is subject to referer spam, in the same volumes.

Referer spam is more visible, in Stats logs with less organic traffic.

Not every blog owner sees referer spam, in their Stats logs, simply because the volume of referer spam is not so heavy, compared to genuine traffic. If I check the Stats logs for this blog, I can generally find the currently mentioned spam domains, reflected in my pageview counts. If I look closely.

To reliably find the referer spam attacking my blog, I have to check my Stats logs frequently. In my case, when I note the domains in question, they will be listed in the "Now" time range - and occasionally in "Today" - when "Now" reflects early morning UTC (just after the daily counts reset).

Some referer spam peaks, during the day - causing visibility fluctuations.

If the referer spammers attack this blog during any other time of the day, the volume of legitimate traffic generally exceeds the referer spam traffic, any time outside "Now". Thanks to the limited function of the Stats logs, referer spam is simply not always visible, because legitimate traffic is more visible.

Google anti-referer spam action also causes visibility fluctuations.

Thanks to regular changes by the spammers, and to ongoing spam blocking by Google, the same domains are not active for more than a week or so. The "Week" and "Month" normal volumes, for this blog, simply exceed the referer spam volumes.

And that's the case for everybody's blog. Check the logs for your blog, if you don't believe me. Just check frequently, and regularly, during a week, for the most accurate conclusion.

And that brings me to my last bit of advice, about the spam.

Concentrate on publishing your blog, and getting legitimate traffic - and the referer spam will not be an important issue.

That's not condescension, or snark - it's simple truth.

Tuesday, May 14, 2013

The Google Apps "bloggeradmin" Password Reset Uses A Standard Google Account Reset

As Google Apps updates their limited function ("bloggeradmin") account setup process, we see reports from confused Blogger blog owners.
After I reset my password, I still get
The username or password you entered is incorrect
when I try to login, later!
and
I reset my password - and it changed my Blogger and GMail account - but I still can't login to Google Apps!!


The Google Apps password reset uses a standard Google account reset process - and is subject to normal account reset behaviour. If you don't reset the right account, you won't be able to login, later.

The Google Apps "bloggeradmin" account setup works best using two browsers.

The password reset, for "bloggeradmin@mydomain.com" (as an example, here) involves a Google account reset.
  1. You start the password reset from a Google Apps login screen, for "mydomain.com".
  2. After clicking on the "Can't access your account?" link, you use a standard Google account reset process.

When you attempt to login to Google Apps, click on "Can't access your account?". That takes you into the Google Account Reset process.


Provide the full account name of your Apps account.
bloggeradmin@mydomain.com
instead of
myemail@gmail.com

If possible, use two different browsers. And, to be safe, clear cache, cookies, and sessions (yes, all 3!) - then restart the second browser, before opening the password reset email.

The password reset will be more likely to be successful, if your Blogger account is based on an active and real email address - this is not a good time to be anonymous.
(Update 2013/11/03): This process should be slightly simplified, with Google Apps now using the new Google comprehensive login screen.


>> Top

Friday, May 10, 2013

Comment Moderation In Blogger Blogs, Using Google+ Comments

With more Blogger blogs being updated to use Google+ Comments, we're seeing a few questions in Blogger Help Forum: How Do I?, about comment moderation.
How do I moderate comments, with Google+ Comments enabled on my blog?

This is a question for which there is no easy answer - and this is one of the least appreciated feature limitations of Google+ Comments.

Native Blogger commenting allowed the option to moderate comments before or after they were published.

Google+ Comments, for Blogger blogs, provides no ability to moderate before publishing. All comments must be moderated after they are published. Moderation now simply consists of the ability to declare a comment as abusive - and this ability is shared equally by all users of Google+, who are in the right Circle to read and mark any comment.

With native Blogger Commenting, you (the blog administrator / owner) could moderate comments (before or after publishing), using either email, or the dashboard Comments section. With Google+ Comments, you have no such ability - and the dashboard won't even have a Comments section, listing comments made against the blog. You can view comments made - when you are able to view them - on a post by post basis, under each post.

As the blog owner, you do not have control over all comments, published against your blog. If you allow comments using Google+, anybody who is in one of your Circles can publish a comment against your blog. If you Share a blog post to the Public - or if someone else Shares a post from your blog to the Public - and a third person comments, you may not even see the comment made, against your blog.

You cannot see comments published by people who are not in your Circles, unless the comments are posted Publicly - even if the comments are published against your blog.

For these reasons, this blog remains with Blogger Commenting.

Thursday, May 9, 2013

Blogger Blogs Redirecting To "opromo . com"

This week, we're seeing a new stream of problem reports, from blog owners whose blogs are, once again, mysteriously redirecting their readers to unknown destinations.
When I open my blog, it automatically directs to another search engine display.

This appears to be yet one more gadget, willingly installed by many Blogger blog owners, which is now redirecting uninterested viewers. The target of the redirection, this week, is a parked domain website (ie, "search engine display") - for a product which was apparently installed, willingly, by the blog owners.

It appears that the "opromo . com" free visitor meter is the latest victim of expiring domain registrations.

Overview for opromo.com

Registrar Info
Name PDR LTD. D/B/A PUBLICDOMAINREGISTRY.COM
Whois Server whois.PublicDomainRegistry.com
Referral URL http://www.PublicDomainRegistry.com
Status clientTransferProhibited

Important Dates
Expires On May 09, 2013
Registered On May 09, 2006
Updated On May 09, 2013
People who earlier installed the Opromo free visitor meter will need to uninstall it, as it's apparently no longer operational. Reliable replacements would be SiteMeter and StatCounter - as well as Google Analytics.

From what we've seen, identification and removal of the problem code seems to be straightforward - just access the dashboard "Layout" menu wizard, find the gadget identified, and remove it.

As always, you are advised to clear cache and restart the browser, after removal and before testing for success. If the gadget makes your dashboard redirect, before you can remove the redirecting code, use a well protected browser, like Firefox with NoScript, to block the redirection.

>> Top

Empty Or New Blogs Can Be Classified As Spam Hosts

We're seeing a few recent reports, in Blogger Help Forum: Something Is Broken, from owners of empty and / or new blogs, about spurious spam classification.

Very few owners of empty or new Blogger blogs understand why their blogs should be classified as possible spam hosts, by the Blogger anti-spam processes. Most blog owners seem to think that only blog content is considered, in spam classification.

Spam classification considers many characteristics of a Blogger blog, in classifying any blog as a possible spam host.

Blog post content is an obvious - but not the only - factor in spam classification. Given previously observed behaviour of spammers, many characteristics of blogs, besides simply the extracted and analysed content, are used in classifying possible spam blogs. Using fuzzy spam classification techniques, one might also consider
  • Accessories and decorations, on the blog.
  • Addresses used, in setting up multiple blogs.
  • Overall behaviour in Google, by the owner.
  • Past posting habits of the owner.
  • Previous classification of similar blogs.

Some spammers obscure their activity, with gratuitous Google activity.

Some spammers are active in multiple Google activities and features. It's possible that some spammers even try to make their spam in Blogger harder to detect, by spreading their activity across other Google services - even when non abusive in other Google services.

Some spammers may not realise that activity in other Google areas can be tracked, and included by Blogger spam classifications processes.

Blog publishers, enjoying similar activities, may be spuriously classified.

Blog owners who use one or more techniques involved in setting up and maintaining spam blog farms may be classified as spammers - and their blogs then classified as possible spam hosts.

The term "blog owner" must itself be considered fuzzily, as some spam blog farms contain blogs owned by multiple Blogger accounts and profiles. Some Blogger accounts, similar to known spammer accounts - even with no blogs owned, or with empty blogs published - may then appear as possible spam hosts.

Empty blogs may still provide clues, which suggest spammy purpose.

Empty blogs, that appear similar to blogs in known spam farms, may themselves be classified as possible spam hosts. Various details such as blog name, blog design, and use of various blog accessories and features, can make a blog appear similar to known spam blogs - with no other content.

As long as spammers exist, some Blogger blogs will be spuriously classified.

Given the need for Google to reduce the volume of spam blogs, fuzzy spam classification might use any of the above details, in classifying any empty or new blog as a possible spam blog. This will, unfortunately, lead to spurious spam blog detection.

The possibility of spurious classification cannot prevent classification, in general.

Given the ability of spammers to publish multiple blogs in the Blogger name space, classifying empty and new blogs is necessary, in making it possible for Google to keep up with spammy activity. This technique enables publishers of genuine blogs to have their blogs viewed as righteous Internet content - not as one more blog, in a sea of spam.

Thursday, May 2, 2013

The Google+ Comments Feature Was Recently Updated - And Is Now Broken

We are seeing an abrupt flood of reports from Blogger blog owners who have accepted Google+ Comments, in their blogs.

It appears that Blogger has fixed the observed problem with the Comment Count not displaying - and has possibly at the same time, broken Google+ Comments, in general.

Blog owners are reporting that comments are simply not visible - even with the Comment Count now showing a non zero value. My test blog is now showing this problem - though it did not, before I updated the post template.

We have a new Rollup Discussion, where everybody observing this problem is invited to provide some diagnostic details.

(Update 2013/05/02 23:00): The problem appears to be resolved.

>> Top

Wednesday, May 1, 2013

Renewing Your Custom Domain Registration

Some Blogger blog owners, having experienced the anxiety of custom domain setup, intend to carefully maintain their domain registration.

We see a few queries, in Blogger Help Forum: How Do I?, about domain registration renewal.
How do I make sure my registration gets renewed?
or
How do I renew registration before it expires?
or, possibly
My blog now displays a search page! Have I been hacked?

Some registration issues will depend upon how the domain registration was originally purchased.

Domains purchased directly from a registrar - whether using eNom, GoDaddy, or a third party registrar, will have to be renewed directly from the registrar. It's not possible to migrate a direct purchase to Blogger / Google registration for payment, any more than to use the Blogger / Google automatic DNS setup. Once you purchase domain registration from a registrar, you are on your own.

If you used Blogger "Buy a domain", Google Apps, or Google Wallet, to purchase the domain registration, you should get email reminders when registration is expiring. However, this will depend upon whether your Blogger / Google account, under which you purchased the registration, uses an active and accessible email address.

If you choose to anonymise yourself by using a bogus or inactive email address for your Blogger or Google activities, don't expect to get email reminding you, or allowing you to renew domain registration.

The most reliable way to assure the domain remains registered is to use domain auto renewal. You can check your auto renewal settings using the Google Apps administrator account, for the domain (now called the "Admin Console"). Be aware of the oddities of the Google One Login wizard, and Google Apps, when logging in.

For domains purchased before December 2012, you'll use email from Google Apps, or an entry in your Google Wallet log, to retrieve the token to setup your Google Apps account. For domains purchased after November 2012, you will have only a limited access Google Apps account, which you should reset the password, to access.

If you intend to use domain auto renewal, make sure that the bank account (credit, or debit) is active, and currently paid. If your bank rejects the payment, you should get a notice - but again, this will come reliably when the email account associated with the domain is active and accessible by you.

Procedures for renewal after expiration are different - and may cost substantially more than the normal yearly fee.

The best renewal experiences, of course, start with advance planning.

>> Top