Enter up to 100 URLs (Each URL must be on separate line)
A website can suddenly come to a halt without a warning and hence, visitors are not able to reach important pages. Free SEO Pro Server Status Checker can perform an investigation to see if website urls respond and which http status codes they return. Up to 100 urls can be entered; one address on each line. It can be very helpful for those who are looking for an overview of broken pages, redirects, and server errors on a website for the website owner, developer, blogger, and SEO professional. Even if you succeed in a good response, it doesn't mean that you can guarantee all visitors can access the website.
A Server Status Checker is an internet based website testing device which looks at responses from web addresses. It distinguishes a page which responds successfully minus a page which is returning an error and/or redirect.
Free SEO Pro's user interface promises to check up to 100 urls and each one must be on a separate line. It points out a Check Server Status action and explains that the users should look into HTTP response codes.
Free Seo Pro
HTTP responses tell us the status of a server's response to a request. These can include successful responses, redirect responses, missing pages, access restrictions, and internal error responses.
These results are for initial trouble shooting purposes. They're not a good stand-in for whole website monitoring, nor do they spell every cause.
Normally, a destination server responds with an HTTP response to a browser or checking service when it requests a webpage. In that response, there is a numerical status code.
Codes in each category are grouped together. The number is broken into the first digit denoting the general response type, and the latter digits denote a more specific condition.
2xx: Successful responses.
3xx: Redirection responses.
Semantic match responses – 4xx – Responses indicating client error (such as missing resources, improper access).
- 5xx: Server error replies.
A website checker can help you explore these answers, instead of manually examining each request with browser developer tools.
The precise method of sending requests, timeout settings, how redirects are handled and how the testing location is set, however, is not documented on the accessible page on Free Seo Pro.
Complete the steps according to instructions that appear on the site.
1) Go to the Server Status Checker page.
2. Gather the URLs of the web pages you wish to analyze.
3. Type in the first full URL in the space.
4. Create additional URLs on new lines.
5. Do not exceed the maximum number of URLs advertised (100).
6. Click Check Server Status to start the checks that you requested.
7. Check back for the data pertaining to every address.
8. Research lone irregular errors or re-directs.
9. Test the site again following repairs to the site.
Use specified protocol and hosts. For instance, https://example.com/ and http://example.com/ might generate different initial responses.
When research is focused on individual articles, product pages or landing pages, adding page paths is helpful. Only checking the homepage will not get an idea of any issues elsewhere.
Suppose that you've updated 5 pages on a gardening website. You want to ensure that users are able to access destinations that they are looking for.
Make a list with your home page, two pages containing articles, and an outdated address.
Let's say that the hypothetical results indicate three successful responses, one permanent redirect and one missing page.
Those responses seem to indicate that the requests were acted upon positively. Redirects should be reviewed to ensure that it is redirecting appropriately to its intended destination, and that the missing page should be investigated.
These are representative results, not actual results from Free SEO Pro. The responses may vary based on website and testing conditions.
An HTTP status code indicates what the result is of a specific request. Understand its meaning with the requested URL and redirect target URL.
Status Meaning Suggested action
00200 OK Check visible content
Frequently used to redirect users to a different, permanent address.
Informational 302 Found - Temporary redirect flag to confirm intended behaviour
403: Forbidden - Evaluate the access controls in place.
404 Not found - Repair or redirect
410 Gone Agreement about removal of item intentionally
500 (Internal server error): Check server logs for information
503 Service unavailable Check maintenance or capacity
A page can 200 with an incorrect content, a blank interface or an application error.
Similarly, a redirect does not always have a negative impact. Redirects can be useful if the URL in the web service has been changed, but needs to be redirected to sensible places.
Test critical URLs following deployments, content migrations or routing rule changes. This can uncover these surprise missing pages ahead of time before users have to report them.
Check the "broken" or "redirected" URLs in Google Search Console. Check server responses search against canonicals, internal links and sitemap listings.
A status check will assist to narrow the investigation. If an error occurs and it seems to come and go, or it only happens at certain spots, then compare results from another network.
Pilot key landing pages before advertising via advertisements, newsletters, or social media. Assert even in cases of a successful return code that the page works.
A frequent error is to consider any NON-200 as a server failure. Some of the responses (e.g. redirects, or authentication requirements) may be on purpose.
One error is only looking at the home page. If one of the subpages is important, it may fail without the main page failing.
If the results appear to be unusual, check the URL or look at the redirects, and use the browser developer tools, or another independent service, to verify the response.
One check = one snapshot - not continuous uptime monitoring. It is unable to determine monthly availability or identify all the short outages.
Even if a site is accessible by a regular user, the security controls can prevent automated requests from accessing the site.
The information published does not provide for automated alerts, historical reporting, downloadable results or guaranteed times of response.
Don't send private administration emails or URLs with sensitive access tokens to a service without being able to know how the service handles requests.
When a site is not available, use Find DNS Records and find out about their domain configuration.
The Whois Checker can be used to perform domain registration research and can be useful in cases of finding expired or not well managed domains.
Check the Robots.txt Generator for Search engine access rules.
XML Sitemap Generator organizes important urls of the website for search engine discovery.
The questions answered by the various tools are different. One aspect of a reliable and accessible web site is having a great answer time from the server.
A Server Status Checker – checks the server response to the request of the website. It will look for successful responses, redirects, missing pages, access restrictions and some of the server errors.
Type in the URL of your site in the checker and begin the test. Check the answers and then test the page for yourself to make sure that its content and features work.
Free SEO Pro's page has a mention of up to 100 URLs. Make sure to input one address per line and check the one line at a time.
Status 200 - indicates that the server has successfully processed the request. It does not verify the accuracy of the webpage content, that it loads entirely, or that it's a nice experience for visitors.
301 – Permanent redirection to a new address. Test destinations, and make sure internal links direct to desired final URL, when applicable.
301 is a permanent redirect (permanent) and 302 is a temporary redirect (temporary). Provide an appropriate response about the permanent redirection to the requested resource.
403 response: This means that the server is rejecting access to the resource that's requested. It may be due to permissions, security rules, authentication limitations or even automated request blocking.
Verify that URL is correct and that the page exists. If necessary, add missing information, or, if relevant, redirect an outdated address to a new one.
Response 500 means there is a problem with the internal server. This could be due to application failures, configuration/setting errors or code errors. Look through the logs of the server and find out what is going wrong.
Can assist the identification of an unavailable website during a check. But no one result can confirm continuous downtime, absence of uptime or how long an outage was.
A tangible improvement in rankings is not guaranteed. Checking responses will allow for the discovery of technical issues that can impact the visitor experience, accessibility, and crawling if not fixed.
Some automated requests may be blocked by the server, some servers may have geographic restrictions, or they may behave differently for some networks than they do for others. Don't assume an outage—compare requests and look at security first.
Description of HTTP / HTTPS Server Response page. If you need to look up a full HTTPS URL, enter it and then make sure that you get the same service result you're expecting.
No. When requested, answers are checked by a man. Uptime monitoring services hold repeated checks and over time can be alerting, incident record and availability report.
Document the affected website addresses, examine the logs and host configuration and fix the issues. Re-check addresses afterwards and check crucial pages in Google Search Console.
