Skip to main content

Timeline for Google crawling/indexing PHP files

Current License: CC BY-SA 3.0

9 events
when toggle format what by license comment
Sep 27, 2013 at 14:36 comment added I.G. Pascual Then you can add that entry to your robots.txt with no fear, robots.txt only block what Google reaches, which are your URLs
Sep 27, 2013 at 14:32 comment added Jimmy My URL's do not have >/content/< anywhere in them. >/content/< is a directory i see in my FTP, my URL's generally are >example.com/catalog/....< or >example.com/catalog/products/...<
Sep 27, 2013 at 14:23 comment added I.G. Pascual No, I confused you, I explained myself wrong: Say your site is www.example.com, if your URLs look like www.example.com/content/..., you have a problem. But if your URLs don't look like www.example.com/content/..., but your php files are located in .../foo/bar/content/ directory then you are ok. Google cannot see your php files, just the URLs you generate with them.
Sep 27, 2013 at 14:10 vote accept Jimmy
Sep 27, 2013 at 14:10 comment added Jimmy Ok, so adding this to robots.txt would be a terrible idea in my situation, being as my site is being generated from this subdirectory. I need to determine why these are all of a sudden being shown to the world, in order to address the root problem. Thanks!
Sep 27, 2013 at 14:00 comment added I.G. Pascual Of course, when I mean pages I also mean php files, as they generate HTML and thus a page to Google. Blocking that subdirectory, you will block Google from indexing all the pages generated by the files under /content :D
Sep 27, 2013 at 13:57 comment added Jimmy Thanks for the help Pascual, to clarify, i don't have pages in this directory, only the files which dynamically generate the pages. By blocking these files, will it then block the pages these files create?
Sep 27, 2013 at 13:53 history edited I.G. Pascual CC BY-SA 3.0
added 216 characters in body
Sep 27, 2013 at 13:46 history answered I.G. Pascual CC BY-SA 3.0