Welcome to the Question2Answer Q&A. There's also a demo if you just want to try it out.
0 votes
1.4k views
in Plugins by
closed by

When crawling the web google reads and abide to robot.txt file.

This robot.txt  file may optionnally contain a line :

Sitemap : http://yourwebsite.com/sitemap.xml (or gz extension ...)

This tells google about the sitemap, so that, after reading robot.txt, google will also read sitemap.xml, and then Google will (try to) index the pages listed in siremap.xml.


When I access the Q2A page <myWebsite>/sitemap.xml, I trigger the Q2A "sitemap plugin", which currently replies to my browser with some xml (the filemap properly formatted in xml). I can read this xml in my browser.  I then have to copy / paste to create a sitemap.xml file that i will transfer in the root folder of my website. 

Could the plugin save the generated sitemap xml data in a file sitemap.xml and place it in the web root directory (instead or in addition to) ?


Also, instead of having to get to my browser and request the url <myWebsite>/sitemap.xml,  it would be fine to get a script that would do the same  (generate and place the file in the root web directory), I could trigger this script with a cron -- my web is hosted by ovh.com and i get a cron service along with my hosting (which is the cheapest one).

Thanks

 

 

Q2A version: Q2A 1.5, XML Sitemap v1.1.1
closed with the note: My question could be deleted. Merkus brought light to me.
by
That's odd. My 1.5 install's sitemap link is sitemap.xml. I just go to Google Webmaster Tools and input mysite/sitemap.xml. Google reads the xml file, and is happily crawling the sitemap links.
by
Do you mean you get a sitemap.xml file generated ? Where is it ? how do you get it ?
by
Yes - mysite/sitemap.xml
by
OK, fine for me.
I was a bit lost and now things are more clear for me.
Thanks.

1 Answer

+1 vote
by

I'm afraid it's not possible for Q2A to modify responses which occur out of the directory it's installed in. But perhaps you could change your robots.txt file, or use a redirect instead?

...