Google Site Map 404 verify code

Does anyone use the Google Site Map XML generator?

I use it on all the sites I create, but Google have just implemented a checking mechanism which requires a valid error code. There was a fix that I’ve been using which involved swapping the index.php with an old eto (modified) index.php which returns a valid error code for the purpose of verifying the site, but results in no managed pretty error page (so only ever been a temporary measure for the verify process).

I’m aware that modx will not operate correctly with an Eto file, it was only to generate the correct verify code. But this method now does not work.

In a future release of Modx, can there be a returned valid error code before the redirect/refresh to a managed error page?

The Google error is...

We have detected that your 404 (file not found) error page returns a status of 200 (OK) in the header.

If others use a Google Site Map with Modx, how have you overcome this problem?

Thanks.

I did this before.

Before you verified you site, change your .htaccess file name into something else, then verify your site. After verifying it, change back your .htaccess.

Regards,
Wendy Novianto

Quote from: wendy at Dec 06, 2005, 02:29 PM

Before you verified you site, change your .htaccess file name into something else, then verify your site. After verifying it, change back your .htaccess.

Why is that the one thing I didn’t think of? LOL! Silly me. Thanks Wendy.

No prob, glad that I could help someone else...

hi everyone ! i disabled rewriting, and renamed htacess files, but i have this message with google sitemaps ... :
Pending verification
The system is currently busy. We will process this verification as soon as possible. Please check back later for an updated status.

how can i solve this ??
thx

Wait on Google??

what do you mean ?? ( sorry english isn’t my native language )

bye

Quote from: chucky at Feb 08, 2006, 09:47 AM

what do you mean ?? ( sorry english isn’t my native language )

bye

Ah same here...
I thought it’s because the server from Google that is overloaded. It’s just a guess. Maybe you need to wait for a while, because it’s not something from MODx I believe.