Bengo's dashboard

These are img src tags.

Right now, I would much rather get my home page repaired, as I have just found it's still unattended. I was forced to use two browsers due to the new image library not functioning on Safari, and no one warned me that there was a risk of cross-contaminating two different open sites. psychedelictreehouse.com has the home page that belongs to lilnyet.com, though only in the editor; not when you visit the sites.

I can't do the image tag work I was planning until this is addressed. I understand it requires the attention of engineering and assume they haven't gotten to it yet.

I would think there would be more of a rush on since this happened as a result of the editor functioning degrading while I am trying to operate web sites. I think all the problems that are affecting me are being sent as notes to the engineering department and no one realizes how truly messed up my functioning is, and how dissatisfied I have become after being a long time enthusiast.

I think I am the guy with the complicated problems and no one wants to deal with me.

Vincent,

If my question was answered, I wouldn't object to getting all the false alerts you are generating in my email, nor would I be terribly concerned about you disrupting the thread.

You are making a pest of yourself and showing poor regard for other users. This is a good way to persuade other users not to try to answer your questions when a company rep is not immediately available.

My advice is to re-think your behavior. You are obviously a young person who is unexperienced with these things, so consider yourself forgiven. Just cut it out. Thanks.

Meanwhile, you might try doing what Monique requests and verifying it. A bad batch of images obviously has a common problem, so this would be wrapped up already if you communicated a little more effectively. I might even help you myself if she is busy.

I checked the WT code in the de-verified domain. The code on the index page differed from any other code I have -- the last seven characters were re-ordered and one changed.
I have no explanation.
Installing the correct code and requesting verification was successful for the domain.
I will not attempt to re-verify any subdomains until I hear from you with guidance.
Appreciate the help!

Thanks for the reply. I want to mention that I think a portion of the tangle is from this:

- You are supposed to install Webmaster Tools code as assigned: each site gets its own code
- Google wants subdomains and domains to each have their own code
- But, we can't access subdomains to install it
- Consequently, I installed subdomain short term on the home page of the domain, which resulted in verification of the subdomain
- I then installed the domain code in its place, replacing the subdomain code
- Now both the domain and subdomain were verified by Google WT
- However, the subdomain code is not published anywhere on the subdomain site now, so any routine check would de-verify it
- This may explain why three of my subdomains have been de-verified, but it does not explain why one domain has been as well. I am going to study that one and report back.

I don't mean to be rude, but this is my post and Vincent can ask his own question on his own post so that perhaps I can get mine answered.

*headdesk*

Hi Kev,

Google Analytics takes 24 hours to produce its first report. Give it a bit more.

The reports often appear in the wee hours, so try checking in the morning.

You picked up a strong link just from posting here, so get your tags in place, update often and it should pop soon.

Bengo

Some interactive sites, like some ad placement sites, have script that looks a bit shaky when it comes to accurately sending information to addresses like that, so it seems like a good idea, especially if you can address it on the GoDaddy level. Unfortunately, that's where my knowledge ends. I cannot comment on server-level settings and interactions. If I find out I'll come back and post again.

I have been trying to sort out the issue of site.synthasite.com vs site.com. SynthaSite is working on a solution but that's all I know. I'm sure the long term fix will be good, but right now I am getting hit with Webmaster Tools de-verifications and possible Google penalties as my search results plunge. They may be seeing the former site as duplicate content or something.

Of course, the SynthaSite staff might have your answer. Good luck.

1/3/09 My most important site has now also been de-verified by Webmaster Tools. To re-verify requires new code, meaning reinstallation on hundreds of pages.

Thanks so much, but this is not about getting verified. It's about figuring out the cause of being de-verified. I appreciate your assistance.

I'm sorry, but there is no message from Google per se.

The information comes from verified sites suddenly becoming unverified on the Webmaster Tools dashboard and the new code they want to assign to the site being different than the old codes.

I think it is caused by the fact that you appear unable enter a subdomain to install Webmaster Tools code. You have to put your subdomain code on the home page of the domain (in the code box), verify (it will be approved) then change the code back to the domain code on the domain home page. I suspect Google has sensed the domain/subdomain difference and has invalidated the verification approach that was previously applied.

I tally these issues with the domain/subdomain arrangement:

- Apparent trouble with Webmaster Tools set-up;
- Possible mis-routing of traffic;
- Content duplication issues. I have read there is a Google penalty risk for domain/subdomain duplication.
- Search muddying, with the subdomain turning up in results;
- People linking to the wrong domain address, wasting links;
- The need to combine two analytics reports for every site when evaluating any parameter;
- Accidental creation of misleading data regarding ad performance;
- The inability to forward subdomain traffic to the domain to create a clear traffic count.

I am not blaming SynthaSite for this! I am building an enterprise just as you are, and as we enter new territory, we do it together, knowing there will be bumps. I couldn't be happier with your staff and product. But in the interest of being clear, I want to report the user experience I have with candor, so that it doesn't spread to others. I think because I am a long time user with multiple sites, some of them hundreds of pages long, I am more likely to notice stuff early, and as much as I want problems relieved, I particularly want to catch them and alert you before they affect others.

What would help me the most:

- Please make sure everyone interested in the domain/subdomain topic is in on these chats, including Chris;
- Keep me up-to-date on what will be happening in the next few months (to the extent you can) so that I can know when to repair and when to await a development. This could save me a lot of work;
- Evaluate my de-verification report from Webmaster Tools and advise, with an eye toward stopping its spread to my other sites;
- Advise if the way I verified subdomains with Webmaster Tools was the way you do it, or should I use another method;
- Have me clarify anything that is unclear.

Chris sent me some subdomain workarounds which are possible but not as attractive as waiting for a more concrete fix, assuming it's in the works. This could change if, for example, Google does a PageRank update for the public and mine is hurt. I understand what PR is and is not, and that it is rather obsolete, but the ways it still functions are important to my sites.

You may not appreciate how much we value your help and personal commitment to assistance. You are immensely appreciated.

Best,
Bengo

This may be caused by not being able to enter my subdomains from the My Sites list in order to insert their code, and having to use the main domain temporarily to do so.

If so, it's sure to hit the other domains, meaning another multi-day, fix-every-page-on-every-site session. That'll be about 1250 pages.

My comic update at LilNyet.com published successfully. I can wait to publish my other large sites until things have had a chance to stabilize. Thank you for keeping us up to date.

Yes, the artwork. Quite a surprise from a stranger. – Bengo, on December 22, 2008 23:09

@Monique: If you think highly of your staff, I bet they will come out of the episode better informed and more prepared than ever. I have been with Synthasite since January 08 and run over 500 pages of web sites. Most of the problems I have had have been my own. Nothing of consequence traces back to the company. I don't think it's too much to have to roll with the rare bad weekend. Obviously, some people may have had different experiences, and I respect that, but I won't lose any sleep, and I hope your engineering team doesn't get too stressed. Thank you for keeping us all informed.

I do sympathize with those others who are posting on deadline to a readership, but a couple of weeks ago, our power went out for three days due to an ice storm. I got a generator running but we were late with our postings and only recovered last Thursday. No one has written us angry mail. That's with over 1200 visitors/day, average. I know many have more, but people understand if you are honest with them. Even some of the biggest sites have technical problems. Today we got an out-of-the-blue Christmas gift from a reader in the UK. It's visible at LilNyet.com. Maybe it will cheer some people up. (scroll to the bottom of the page)