CODEWITHSUNDEEP
phprefreshhttp-equiv
Avigail
Avigail

Reputation: 11

Purpose of <meta http-equiv="refresh"> with recursive URL in a separate file

Google has been visiting a site file, 'test3.php', many, many times. I'm wondering if this could have any effect on our SEO, if it shows a fault in the coding, or if it part of the design for this site -- simply a way to refresh pages using a separate file. And if so, is this a good practice?

This is the content of the file:

    <?phpsession_start();?><html><head><meta http-equiv="refresh" content="60;url=test3.php" /></head><body bgcolor="#ffffff"></body></html>

Most of the pages on the site refer to this file, and a sitemap shows it's there, although there is no 'test3.php' visible in the code of any of those pages.

Is this code necessary? Advisable?

And every 60 seconds, as you might expect, livehttpheaders Generator tab shows this activity: 

    GET /test3.php   #request# GET http://www.mysite.net/test3.php   GET /test3.php

etc.

Upvotes: 1

Views: 6432

Answers (1)

Purus
Purus

Reputation: 5799

As you know, http-equiv="refresh" is for refreshing a page for x seconds.

<head>
   <meta http-equiv="refresh" content="30">
</head>

The above code will refresh the document every 30 seconds.

Search engines usually don't like it. So my suggestion is not to use it.

some Info on recommendation on usage: http://en.wikipedia.org/wiki/Meta_refresh

Upvotes: 2

Related Questions