Test #1 – Do you know if your site is responsive?
- Are you getting the most out of your website? Mobile responsive websites are more important for your business than ever:
An overwhelming amount of website searches, carried out on mobile phone, lead to action in a very short time frame. Many local searches on mobile phones lead to an instant phone call.
- Mobile phones account for 3 out of every 5 searches, and almost 75% of Smartphone owners use their phones for getting directions.
… and this is still growing rapidly.
- Most importantly – As of 2017, Your site wont rank as highly in search engines if it’s not responsive.
A Mobile friendly website is now recommended by Google itself. Google controls over 65% of the search browser share. Google’s stance on ideal mobile configuration has always been Responsive Web Design. Google has advocated Responsive Web Design as the industry best practice. Google is now as of 2017, indexing only the mobile version of websites. Meaning your mobile reponsivity is more important than ever. Google won’t favour your site, if it is unresponsive.
- Test Your Website! Use Google’s Website Responsiveness test to see if your website is Mobile Friendly today:
Another reason Google favours responsive website design is because Responsive Website Design delivers a better experience for your clients navigating your site for what they’re interested in. Websites built solely for desktops do not deliver a good user experience when accessed via Smartphone.
Your website will also remain consistent from mobile to desktop. If your business website is mobile-friendly, you will attract and keep more clients.
If your business’s website is mobile unfriendly, over half of mobile users will be discouraged and may even stop engaging with your site. If your website loads quickly and has easy navigation, your customers will be much more likely to buy from you, and even recommend you.
However, If your website loads slowly and needs constant zooming in on products to read them, your customers are less likely to buy from you.
Setting up a mobile website for your business doesn’t mean beginning from scratch. Your current website can be completely optimised to be mobile friendly. Burst creative offers this service and will happily discuss the best solution for your needs with you today.
The Fetch as Google tool enables you to test how Google sees your site. You can use “Fetch as Google” to see whether Googlebot can access pages on your site, how the page renders, and whether any resourcesare blocked to Google. This tool is useful for debugging any issues on your site.
Fetch This is a relatively quick operation that you can use to check or debug suspected network connectivity or security issues with your site. Fetch does not request any associated resources (like images or scripts)
Fetch and render Fetches a specified URL in your site, and also renders the page according to your specified platform (desktop or smartphone). This operation requests and runs all resources on the page (such as images and scripts). You can use this to detect visual differences between how Google sees your page and how a user sees your page.
What does it mean?
Complete Google successfully contacted your site and crawled your page, and can get all resources referenced by the page. Click the table row to see more details about the fetch results.
Partial Google got a response from your site and fetched the URL, but could not reach all resources referenced by the page because they were blocked by robots.txt files. If this is a fetch only, do a fetch and render.
Redirected The server responded with a redirect. The Fetch as Google tool does not follow redirects. Although the actual Google crawler follows redirects, the Fetch as Google tool will not.
Not found The resource could not be found (404 or 410 HTTP response codes).
This error indicates that you might see the HTTP 404 error code when you access your page using a web browser.
Googlebot isn’t authorized to access the page (for example, if the page requires a password).
This error indicates that you might see the HTTP 403 error code when you access your page using a web browser.
DNS not found
Google couldn’t retrieve the resource because the domain name wasn’t found.
Make sure that you typed in your domain name properly (for example, www.example.com) so that Google can find your site server.
The resource’s host is blocking access to Googlebot by means of a robots.txt file.
Blocked resources can affect Google’s understanding of the page, and the page ranking for specific queries. Blocked resources have a Severity value that estimates the importance of the resource in Google’s understanding of the page:
The resource host either took too long to reply or refused the request.
1) Fetch as Google can’t currently fetch your URL because the server took too long to reply.
2) Fetch as Google cancelled your fetch because too many consecutive requests were made to the server for different URLs. Note the URL is not unreachable for all of Google– it is just unreachable for the Fetch as Google simulation tool.
An unspecified error prevented Google from completing the fetch.