How To Redirect Mobile Users On Your Website

when someone from a mobile device visits a website, i want to redirect that person to a mobile website. Although our mobile platform does this natively, we thought it would be useful to share the redirection code.

It is best if this code is placed between and so it can be recognized first and redirect any mobile users quickly:

What this code does is it says, "If the screen size of the device viewing this website is less than 800 pixels wide, then redirect them to http://yourdomain.com/mobile/" (replace this with anything).

This can also be used to redirect mobile visitors to a YouTube video, a specific page on your website, or something else. A specific page on your website may be best (so they can still click around and access other parts of your website).

Update:

Since the sizes of mobile screens vary so much, it is best to detect by user agent. We suggest following these steps to set up more accurate mobile redirection:

1. Download the Javascript version from http://detectmobilebrowsers.com and save to desired folder (eg. /javascript). Let's name it redirect.js.

2. Edit redirect.js, find and change http://detectmobilebrowser.com/mobile to you mobile URL.

3. In your website header between and , add within head tags.

Source: http://notixtech.com/blog/how-redirect-mobile-users-your-website

What is malware?

If your site has been infected, it is generally because some vulnerability has allowed a hacker to take control of your site. The hacker may change the content of the site (for example, to add spam), or add additional pages to the site, usually with the intent of phishing (tricking users into parting with personal and credit card information). Alternatively, they may inject malicious code (malware)—for example, scripts or iFrames that pull content from another website that tries to attack any computer that views the page.

The term "malware" covers all sorts of malicious software designed to harm a computer or network. Kinds of malware include (but are not limited to) viruses, worms, spyware, and Trojan horses. Once a site or computer has been compromised, it can be used to host malicious content such as phishing sites (sites designed to trick users into parting with personal and credit card information). Some hackers may even take administrative control over a hacked site.

Very rarely, it can take up to a day for malware warnings (and links to the malware review request form) to be visible in Webmaster Tools after your search has been flagged in search results. If you don't see a warning in Webmaster Tools, but your site is flagged, please check back later.

How do I know if my site's been infected?

You can find out if your site has been identified as a site that may host or distribute malicious software (one type of "badware") by checking the Webmaster Tools home page. (Note: you need to verify site ownership to see this information.) We also send notices to webmasters of affected sites at the following email addresses for the site:

• abuse@

• admin@

• administrator@

• contact@

• info@

• postmaster@

• support@

• webmaster@

This identification is based in part on guidelines set by StopBadware.org. However, Google uses its own criteria, procedures, and tools to identify sites that host or distribute badware. In some cases, third parties can add malicious code to legitimate sites, which would cause us to show the warning message. If you feel your site has been mistakenly identified, or if you make changes to your site so that it no longer hosts or distributes malicious software and you secure your site so that it is no longer vulnerable to the insertion of badware, you can request that your site be reviewed (see below).

To protect users and communicate with owners of hacked sites, Google uses automatic scanners to constantly look for these sorts of web pages. If the hacker inserted malware into your site, we'll also identify your site as infected in our search results to protect other users. Any determination that your site is infected is based purely on the content of the infected pages, and not on your reputation as a webmaster.

If your site is infected: How to clean up a hacked site.

If Google detects that your site has been compromised, we'll tell you about it in Webmaster Tools (to ensure that you're notified quickly, you can have your Message Center messages forwarded to your email account). If the hacker inserted malware into your site, we'll also identify your site as infected in our search results to protect other users.

If your site has been hacked or infected with malware, you should act quickly to repair the damage. Google recommends reviewing the recommendations provided by the organization antiphishing.org.

Whatever your platform or type of infection, Google recommends the following steps:

1: Quarantine your site

It's extremely important that you take action to prevent your site from infecting others and to prevent hackers from further abusing the system.

Take your site down immediately. It's extremely important that you take action to prevent your site from infecting others.

Contact your web hoster. If the attack affects other sites they host, they may already be taking steps to address the problem.

Change the passwords for all users and all accounts (for example, FTP access, administrator account, content management system authoring accounts). Check your users: It's possible that the hacker created one or more new accounts. Password guidelines.

If you have access to your server, Google recommends configuring it to return a 503 status code. Taking your site offline is better than using robots.txt to prevent it from being crawled.

2: Assess the damage

Once you've locked down your site, you'll need to identify the scope and scale of the damage that's been caused. Google recommends the following steps:

Visit the Google SafeBrowsing diagnostics page for your site (http://www.google.com/safebrowsing/diagnostic?site=www.example.com) (replace www.example.com with the URL of your own site) to see specific information about what Google's automatic scanners have found.

Scan your computer using an up-to-date scanning program to identify any malicious code the hackers might have added. Be sure to scan all your content, not just text-based files, as malicious content can often be embedded in images.

If your site has been infected with malware, check the Malware page in Webmaster Tools. (On the site dashboard, click Health and then click Malware.) This page lists sample URLs from your site that have been identified as containing malicious code. Sometimes hackers will add new URLs to your site for their nefarious purposes (for example, phishing). Use the URL Removal tool in Webmaster Tools to request removal of hacked pages or URLs. This will prevent the hacked pages from being served to users.

Report phishing pages to the Google Safe Browsing team.

Use the Fetch as Google tool in Webmaster Tools to detect malware that might be hidden from the users' browsers, but served to Google's search engine crawler.

Review the antiphishing.org recommendations on dealing with hacked sites.

If you have other sites, check to see if these have also been hacked.

If you have access to your server, follow these additional steps:

Check to see if any open redirects in your site have been exploited.

Check your .htaccess file (Apache) or other access control mechanisms depending on your website platform for any malicious changes.

Check your server logs to see when files were hacked (bearing in mind that hackers can alter your logs). Look for suspicious activity such as failed sign-in attempts, command history (especially as root), or unknown user accounts.

3: Clean up your site

Clean up your content, removing any pages that were added, any spammy content, and any suspicious code identified by virus scanners or the Malware Details tool. If you have backups of your content, consider deleting your content entirely and replacing it with your last known good backup (once you've checked to make sure it's clean and free of hacked content). You can check whether you've completely cleaned out the hacked content by using the Fetch as Google tool in Webmaster Tools.

If you have access to your server, Google recommends the following steps:

Update any software packages to the latest version. Google recommends doing a complete reinstall of your OS from a trusted source to be sure that you've removed everything the hacker may have done. Also make sure to reinstall or update blogging platforms, content management systems, or any other type of third-party software installed.

Once you feel confident that your site is clean, change your passwords again.

Get your system back online. Change your server's configuration so that it no longer returns a 503 status code and perform any other necessary steps to make your site publicly available.

If you used the URL Removal tool to request removal of any URLs that are now clean and ready to appear again in search results, use the same tool to revoke your request.

4: Ask Google to review your site

If your site was infected with malware

Once you're sure that all malicious code has been removed, you can request a malware review of your site. Google will check your site and, if no malware is detected, will remove the warning label that appears in your site's listing on the search results page.

On the Webmaster Tools Home page, select the site you want.

Click Health, and then click Malware.

Click Request a review.

Once it's confirmed that your site is clean, it can take up to a day or so for the malware warning to be removed from your site in search results.

If the hackers put spam on your site

Once your site is completely free of spam, you can ask Google to reconsider it for inclusion in search results. To request reconsideration of your site:

Sign in to Webmaster Tools with your Google Account.

Make sure you have added and verified the site you want reconsidered.

Request reconsideration of your site.

source: https://support.google.com/webmasters/answer/163633?hl=en&ref_topic=2365140#1

Pagination and SEO

Pagination and SEO

Sites paginate content in various ways. For example:

• News and/or publishing sites often divide a long article into several shorter pages.
• Retail sites may divide the list of items in a large product category into multiple pages.
• Discussion forums often break threads into sequential URLs.

If you paginate content on your site, and you want that content to appear in search results, we recommend one of the following three options.

• Do nothing. Paginated content is very common, and Google does a good job returning the most relevant results to users, regardless of whether content is divided into multiple pages.
• Specify a View All page. Searchers commonly prefer to view a whole article or category on a single page. Therefore, if we think this is what the searcher is looking for, we try to show the View All page in search results. You can also add arel="canonical" link to the component pages to tell Google that the View All version is the version you want to appear in search results.
• Use rel="next" and rel="prev" links to indicate the relationship between component URLs. This markup provides a strong hint to Google that you would like us to treat these pages as a logical sequence, thus consolidating their linking properties and usually sending searchers to the first page.

Using rel="next" and rel="prev"

You can use the HTML attributes rel="next" and rel="prev" to indicate the relationship between individual URLs. Using these attributes is a strong hint to Google that you want us to treat these pages as a logical sequence.

Let's say you have content paginated into the following URLs:

http://www.example.com/article-part1.html
http://www.example.com/article-part2.html
http://www.example.com/article-part3.html
http://www.example.com/article-part4.html

1. In the <head> section of the first page (http://www.example.com/article-part1.html), add a link tag pointing to the next page in the sequence, like this:

   <link rel="next" href="http://www.example.com/article-part2.html">

   Because this is the first URL in the sequence, there’s no need to add markup forrel="prev".
2. On the second and third pages, add links pointing to the previous and next URLs in the sequence. For example, you could add the following to the second page of the sequence:

   <link rel="prev" href="http://www.example.com/article-part1.html">
   <link rel="next" href="http://www.example.com/article-part3.html">
   

3. On the final page of the sequence (http://www.example.com/article-part4.html>), add a link pointing to the previous URL, like this:

   <link rel="prev" href="http://www.example.com/article-part3.html">

   Because this is the final URL in the sequence, there’s no need to add arel="next" link.

"Google treats rel="previous" as a syntactic variant of rel="prev". Values can be either relative or absolute URLs (as allowed by the <link> tag). And, if you include a <base> link in your document, relative paths will resolve according to the base URL.

Some things to note:

• rel="prev" and rel="next" act as hints to Google, not absolute directives.


• If a component page within a series includes parameters that don't change the page's content, such as session IDs, then the rel="prev" and rel="next" values should also contain the same parameters. This helps our linking process better match corresponding rel="prev" and rel="next" values. For example, the page http://www.example.com/article?story=abc&page=2&sessionid=123 should contain the following:

  <link rel="prev" href="http://www.example.com/article?story=abc&page=1&sessionid=123" />
  <link rel="next" href="http://www.example.com/article?story=abc&page=3&sessionid=123" />
  



• rel="next" and rel="prev" are orthogonal concepts to rel="canonical". You can include both declarations. For example, http://www.example.com/article?story=abc&page=2&sessionid=123 may contain:

  <link rel="canonical" href="http://www.example.com/article?story=abc&page=2"/>
  <link rel="prev" href="http://www.example.com/article?story=abc&page=1&sessionid=123" />
  <link rel="next" href="http://www.example.com/article?story=abc&page=3&sessionid=123" />
  



• If Google finds mistakes in your implementation (for example, if an expectedrel="prev" or rel="next" designation is missing), we'll continue to index the page(s), and rely on our own heuristics to understand your content.