{"id":25565,"date":"2026-09-05T02:45:43","date_gmt":"2026-09-04T23:45:43","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/mobile-site-and-mobile-first-indexing-best-practices\/"},"modified":"2026-09-06T00:51:38","modified_gmt":"2026-09-05T21:51:38","slug":"mobile-site-and-mobile-first-indexing-best-practices","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/mobile-site-and-mobile-first-indexing-best-practices\/","title":{"rendered":"Mobile site and mobile-first indexing best practices"},"content":{"rendered":"<p>\n  Google uses the mobile version of a site&#8217;s content, crawled with the<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/google-crawlers\/\">smartphone agent<\/a>,<br \/>\n  for indexing and ranking. This is called <b>mobile-first indexing<\/b>.\n<\/p>\n<div class=\"video-wrapper\">\n<\/div>\n<p>\n  While it&#8217;s not required to have a mobile version of your pages to have your content included<br \/>\n  in Google&#8217;s Search results, it is very strongly recommended. These best practices apply to<br \/>\n  mobile sites in general, and by definition to mobile-first indexing.\n<\/p>\n<p>\n  To make sure that your users have the best experience, follow the best practices detailed in<br \/>\n  this guide.\n<\/p>\n<h2 id=\"mobile-site\" tabindex=\"-1\">Create a mobile-friendly site<\/h2>\n<p>\n  If you haven&#8217;t already, create a mobile-friendly website so your users visiting your site<br \/>\n  through a mobile phone can have a stellar experience. There are three configurations you can<br \/>\n  choose from to create a mobile-friendly site:\n<\/p>\n<ul>\n<li>\n    <a href=\"https:\/\/web.dev\/learn\/design\" class=\"external-link\"><b>Responsive design:<\/b><\/a><br \/>\n    Serves the same HTML code on the same URL regardless of the users&#8217; device (for example,<br \/>\n    desktop, tablet, mobile, non-visual browser), but can display the content differently based<br \/>\n    on the screen size. <strong>Google recommends Responsive Web Design because it&#8217;s the easiest<br \/>\n    design pattern to implement and maintain.<\/strong>\n  <\/li>\n<li>\n    <b>Dynamic serving:<\/b> Uses the same URL regardless of device. This<br \/>\n    configuration relies on<br \/>\n    <a href=\"https:\/\/en.wikipedia.org\/wiki\/Browser_sniffing\" class=\"external-link\"><code>user-agent<\/code> sniffing<\/a><br \/>\n    and the<br \/>\n    <a href=\"https:\/\/developer.mozilla.org\/docs\/Web\/HTTP\/Headers\/Vary\" class=\"external-link\"><code>Vary: user-agent<\/code> HTTP response header<\/a><br \/>\n    to serve a different version of the HTML to different devices.\n  <\/li>\n<li id=\"separate-urls\">\n    <b>Separate URLs:<\/b> Serves different HTML to each device, and on separate URLs.<br \/>\n    Like dynamic serving, this configuration relies on the <code>user-agent<\/code> and<br \/>\n    <code>Vary<\/code> HTTP headers to redirect users to the device-appropriate version of the<br \/>\n    site.\n  <\/li>\n<\/ul>\n<p>\n  The contents of this guide only apply to dynamic serving and separate URL configurations. In<br \/>\n  case of responsive design, the content and the metadata are the same on the mobile and desktop<br \/>\n  version of the pages.\n<\/p>\n<aside class=\"note\">\n  <b>If you use a CMS, such as Wix or Blogger<\/b>, you might need to find a new mobile-friendly<br \/>\n  theme for your site if you can&#8217;t modify your existing theme. Try searching for the name of<br \/>\n  your CMS and &#8220;mobile friendly&#8221;, for example, &#8220;wix mobile friendly&#8221;.<br \/>\n<\/aside>\n<h2 id=\"googlebot-can-see-content\" tabindex=\"-1\">Make sure that Google can access and render your content<\/h2>\n<p>Make sure that Google can access and render your mobile page content and resources.<\/p>\n<ul>\n<li>\n    <b>Use the same <span>robots<\/span> <code>meta<\/code> tags on the mobile and desktop site.<\/b><br \/>\n    If you use a different <span>robots<\/span> <code>meta<\/code> tag on the mobile site (especially the<br \/>\n    <code>noindex<\/code> \u0438\u043b\u0438 <code>nofollow<\/code> tags), Google may fail to crawl and index your<br \/>\n    page when your site is enabled for mobile-first indexing.\n  <\/li>\n<li>\n    <b>Don&#8217;t lazy-load primary content upon user interaction.<\/b> Google won&#8217;t load<br \/>\n    content that requires user interactions (for example, swiping, clicking, or typing) to load.<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/fix-lazy-loaded-content\/\">Make sure that Google can see lazy-loaded content<\/a>.\n  <\/li>\n<li>\n    <b>Let Google crawl your resources.<\/b> Some resources have different URLs on the<br \/>\n    mobile site from those on the desktop site. If you want Google to crawl your URLs, make sure<br \/>\n    that you&#8217;re not blocking the URL with the<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/robots-txt-syntax\/#disallow\"><code>disallow<\/code> rule<\/a>.\n  <\/li>\n<\/ul>\n<h2 id=\"content-is-same\" tabindex=\"-1\">Make sure that content is the same on desktop and mobile<\/h2>\n<p>\n  Even with the equivalent content, differences in DOM or layout between desktop and mobile page<br \/>\n  can result in Google understanding the content differently. However having the same content on<br \/>\n  the desktop and mobile version ensures that the two versions can rank for the same keywords.\n<\/p>\n<ul>\n<li>\n    <b><br \/>\n      Make sure that your mobile site contains the same content as your desktop site.<br \/>\n    <\/b><br \/>\n    If your mobile site has less content than your desktop site, consider updating your mobile<br \/>\n    site so that its primary content is equivalent to your desktop site. You can have a<br \/>\n    different design on mobile to maximize user experience (for example, moving content into<br \/>\n    accordions or tabs); just make sure that the content is equivalent to the desktop site,<br \/>\n    since indexing on your site comes from the mobile site.<\/p>\n<aside class=\"warning\">\n      If it&#8217;s your intention that the mobile page should have less content than the desktop<br \/>\n      page, you can expect some traffic loss when your site is enabled mobile-first indexing,<br \/>\n      since Google can&#8217;t get as much information from your page as before. Instead of removing<br \/>\n      content, consider moving content into accordions or tabs to save space.<br \/>\n    <\/aside>\n<\/li>\n<li>\n    <b><br \/>\n      Use the same clear and meaningful headings<\/b> on the mobile site as you do on the<br \/>\n      desktop site.<br \/>\n    <\/b>\n  <\/li>\n<\/ul>\n<h2 id=\"structured-data\" tabindex=\"-1\">Check your structured data<\/h2>\n<p>\n  If you have structured data on your site, make sure that it&#8217;s present on both versions of your<br \/>\n  site. Here are some specific things to check:\n<\/p>\n<ul>\n<li>\n    <b>Make sure that your mobile and desktop sites have the same structured data.<\/b><br \/>\n    If you have to prioritize which types you add to your mobile site, start with<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/breadcrumb-breadcrumblist-structured-data\/\"><code>\u041d\u0430\u0432\u0438\u0433\u0430\u0446\u0438\u043e\u043d\u043d\u0430\u044f \u0446\u0435\u043f\u043e\u0447\u043a\u0430<\/code><\/a>,<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/introduction-to-product-structured-data\/\"><code>Product<\/code><\/a>, and<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/video-videoobject-clip-broadcastevent-structured-data\/\"><code>VideoObject<\/code><\/a><br \/>\n    structured data.\n  <\/li>\n<li>\n    <b>Use correct URLs in structured data.<\/b> Make sure that URLs in the structured<br \/>\n    data on the mobile versions are updated to the mobile URLs.\n  <\/li>\n<li>\n    <b>If you use Data Highlighter, train it on your mobile site.<\/b> If you use<br \/>\n    <a href=\"https:\/\/support.google.com\/webmasters\/answer\/2692911\" class=\"external-link\">Data Highlighter<\/a><br \/>\n    to provide structured data, regularly check the<br \/>\n    <a href=\"https:\/\/www.google.com\/webmasters\/tools\/data-highlighter\" class=\"external-link\">Data Highlighter dashboard<\/a><br \/>\n    for extraction errors.\n  <\/li>\n<\/ul>\n<h2 id=\"metadata\" tabindex=\"-1\">Put the same metadata on both versions of your site<\/h2>\n<p>\n  Make sure that the<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/title-links\/#page-titles\"><code>title<\/code> element<\/a> and<br \/>\n  the<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/snippets\/#meta-descriptions\">meta description<\/a> are<br \/>\n  equivalent across both versions of your site.\n<\/p>\n<h2 id=\"ads\" tabindex=\"-1\">Check the placement of your ads<\/h2>\n<p>\n  Don&#8217;t let ads harm your mobile page ranking. Follow the<br \/>\n  <a href=\"https:\/\/www.betterads.org\/standards\/\" class=\"external-link\">Better Ads Standard<\/a><br \/>\n  when displaying ads on mobile devices. For example, ads at the top of the page can take up too<br \/>\n  much room on a mobile device, which is a bad user experience\n<\/p>\n<h2 id=\"check-visual-content\" tabindex=\"-1\">Check visual content<\/h2>\n<h3 id=\"check-images\" tabindex=\"-1\">Check your images<\/h3>\n<p>\n  Make sure that the images on your mobile site follow the<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/images-best-practices\/\">image best practices<\/a>. In particular, we<br \/>\n  recommend that you:\n<\/p>\n<ul>\n<li>\n    <b><br \/>\n      Provide<br \/>\n      <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/images-best-practices\/#good-quality-photos\">high quality images<\/a>.<br \/>\n    <\/b> Don&#8217;t use images that are too small or have a low resolution on the mobile site.\n  <\/li>\n<li>\n    <b><br \/>\n      Use a<br \/>\n      <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/images-best-practices\/#supported-image-formats\">supported format for images<\/a>.<br \/>\n    <\/b> Don&#8217;t use unsupported formats or tags. For example, Google supports SVG format<br \/>\n    images, but our systems can&#8217;t index a .jpg image in the <code>&lt;image&gt;<\/code> tag<br \/>\n    inside an inline SVG.\n  <\/li>\n<li>\n    <b>Don&#8217;t use URLs that change every time the page loads for images.<\/b> Google<br \/>\n    won&#8217;t be able to process and index your resources properly if you use constantly-changing<br \/>\n    URLs for them.\n  <\/li>\n<li>\n    <b><br \/>\n      Make sure that the mobile site has the same alt text for images as the desktop site.<br \/>\n    <\/b> Use<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/images-best-practices\/#descriptive-alt-text\">descriptive alt text<\/a><br \/>\n    for images on your mobile site as you do on your desktop site.\n  <\/li>\n<li>\n    <b><br \/>\n      Make sure that the mobile page content quality is as good as the desktop page.<br \/>\n    <\/b> Use the same<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/images-best-practices\/#descriptive-titles-captions-filenames\">titles, captions, filenames, and text<\/a><br \/>\n    relevant to the images on the mobile site as you do for the desktop site.\n  <\/li>\n<\/ul>\n<aside class=\"warning\">\n  <b>If your site is using different image URLs for the desktop and mobile site, you may<br \/>\n    see a temporary image traffic loss while your site transitions to mobile-first indexing.<br \/>\n  <\/b> This is because the image URLs on the mobile site are new to Google indexing, and<br \/>\n  it will take some time for the new image URLs to gain enough historical search results to get<br \/>\n  a better ranking. To avoid a temporary image traffic loss, use the same image URLs across both<br \/>\n  versions of your site. If you don&#8217;t mind a temporary image traffic loss, you don&#8217;t need to<br \/>\n  take any action.<br \/>\n<\/aside>\n<h3 id=\"check-videos\" tabindex=\"-1\">Check your videos<\/h3>\n<p>\n  Make sure that the videos on your mobile site follow the<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/video-search\/\">video best practices<\/a>. In particular, we<br \/>\n  recommend that you:\n<\/p>\n<ul>\n<li>\n    <b>Don&#8217;t use URLs that change every time the page loads for your videos.<\/b><br \/>\n    Google won&#8217;t be able to process and index your resources properly if you use constantly<br \/>\n    changing URLs for them.\n  <\/li>\n<li>\n    <b><br \/>\n      Use a <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/video-search\/#file-types\">supported format<\/a><br \/>\n    <\/b> for your videos and put videos in supported tags. Videos are identified in the<br \/>\n    page by the presence of an HTML tag, for example: <code>&lt;video&gt;<\/code>,<br \/>\n    <code>&lt;embed&gt;<\/code>, or <code>&lt;object&gt;<\/code>.\n  <\/li>\n<li>\n    <b>Use the same video structured data<\/b> on both your mobile site and desktop<br \/>\n    site. For more information, <a href=\"#structured-data\">check your structured data<\/a>.\n  <\/li>\n<li>\n    <b><br \/>\n      Place the video in an easy to find position on the page when viewed on a mobile device.<br \/>\n    <\/b> For example, it might harm the video&#8217;s ranking if users need to scroll down too<br \/>\n    much to find the video on mobile page.\n  <\/li>\n<\/ul>\n<h2 id=\"additional-best-practices\" tabindex=\"-1\">Additional best practices for separate URLs<\/h2>\n<p>\n  If your site has separate URLs for the desktop and mobile versions of a page (also known as<br \/>\n  m-dot), we recommend the following additional best practices:\n<\/p>\n<ul>\n<li>\n    <b><br \/>\n      Make sure that the error page status is the same on both the desktop and mobile sites.<br \/>\n    <\/b> If a page on your desktop site serves normal contents and your mobile site&#8217;s<br \/>\n    version of that page serves an error page, this page will be missing from the index.\n  <\/li>\n<li>\n    <b>Make sure that your mobile version doesn&#8217;t have URL fragments.<\/b> The fragment<br \/>\n    part of the URL is the end of the URL that starts with <code>#<\/code>. Most of the time,<br \/>\n    URL fragments are not indexable, these pages will be missing from the index after your<br \/>\n    domain is enabled for mobile-first indexing.\n  <\/li>\n<li>\n    <b><br \/>\n      Ensure that the desktop versions that serve different contents have equivalent mobile<br \/>\n      versions.<br \/>\n    <\/b> If different URLs redirect to the same URL (for example, to the home page on mobile<br \/>\n    devices) after your domain is enabled for mobile-first indexing, all these pages will be<br \/>\n    missing from the index.\n  <\/li>\n<li>\n    <b><br \/>\n      Verify both versions of your site in<br \/>\n      <a href=\"https:\/\/search.google.com\/search-console\" class=\"external-link\">Search Console<\/a><br \/>\n    <\/b> to make sure that you have access to data and messages for both versions. Your<br \/>\n    site may experience a data shift when Google switches to mobile-first indexing for your<br \/>\n    site.\n  <\/li>\n<li>\n<p>\n      <b>Check <code>hreflang<\/code> links on separate URLs.<\/b> When you use<br \/>\n       <code>rel=hreflang<\/code><br \/>\n      <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/localized-versions\/\"><code>link<\/code> elements<\/a><br \/>\n      for<br \/>\n      <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/managing-multi-regional-and-multilingual-sites\/\">internationalization<\/a>,<br \/>\n      link between mobile and desktop URLs separately. Your mobile URLs&#8217; <code>hreflang<\/code><br \/>\n      must point to mobile URLs, and similarly desktop URL <code>hreflang<\/code> must point to<br \/>\n      desktop URLs.\n    <\/p>\n<p>\n      Here&#8217;s an example of <code>hreflang<\/code> for the home page of a site with separate URLs<br \/>\n      for mobile and desktop.\n    <\/p>\n<div class=\"ds-selector-tabs\">\n<section>\n<h3 id=\"mobile\" tabindex=\"-1\">Mobile<\/h3>\n<p>In this example, the mobile site URL is <code>https:\/\/m.example.com\/<\/code>.<\/p>\n<div><\/div>\n<\/section>\n<section>\n<h3 id=\"desktop\" tabindex=\"-1\">Desktop<\/h3>\n<p>In this example, the desktop site URL is <code>https:\/\/example.com\/<\/code>.<\/p>\n<div><\/div>\n<\/section><\/div>\n<\/li>\n<li>\n    <b>Ensure that your mobile site has enough capacity<\/b> to handle a potential<br \/>\n    increase in<br \/>\n    <a href=\"https:\/\/support.google.com\/webmasters\/answer\/35253\" class=\"external-link\">crawl rate<\/a><br \/>\n    on the mobile version of your site.\n  <\/li>\n<li>\n    <b><br \/>\n      Verify that your<br \/>\n      <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/robots-txt-intro\/\">robots.txt rules<\/a><br \/>\n    <\/b> work as you intend for both versions of your site. The robots.txt file lets you<br \/>\n    specify which parts of a website may be crawled or not. In most cases, use the same<br \/>\n    robots.txt rules for both mobile and desktop versions of your site.\n  <\/li>\n<li>\n<p>\n      <b><br \/>\n        Use the correct <code>rel=canonical<\/code> and <code>rel=alternate<\/code><br \/>\n        <code>link<\/code> elements<br \/>\n      <\/b> between your mobile and desktop versions. The desktop URL is always the canonical,<br \/>\n       and the mobile version is the alternate of that URL.\n    <\/p>\n<p>\n      Here&#8217;s an example of <code>rel=canonical<\/code> and <code>rel=alternate<\/code> for a<br \/>\n      separate URLs site setup.\n    <\/p>\n<div class=\"ds-selector-tabs\">\n<section>\n<h3 id=\"mobile_1\" tabindex=\"-1\">Mobile<\/h3>\n<p>\n          In this example, the mobile site URL is <code>https:\/\/m.example.com\/<\/code> and<br \/>\n          includes a <code>link<\/code> element that points to the desktop URL as<br \/>\n          the canonical URL.<\/p>\n<div><\/div>\n<\/section>\n<section>\n<h3 id=\"desktop_1\" tabindex=\"-1\">Desktop<\/h3>\n<p>\n          In this example, the desktop site URL is <code>https:\/\/example.com\/<\/code> and<br \/>\n          includes a <code>link<\/code> element that points to itself as the canonical URL,<br \/>\n          followed by another <code>link<\/code> element that points to the mobile version as the<br \/>\n          alternate version of this URL.<\/p>\n<div><\/div>\n<\/section><\/div>\n<\/li>\n<\/ul>\n<h2 id=\"troubleshooting\" tabindex=\"-1\">Troubleshooting<\/h2>\n<p>\n  Here&#8217;s a list of the most common errors that can stop sites from being enabled for<br \/>\n  mobile-first indexing or could cause a drop in ranking after a site is enabled for<br \/>\n  mobile-first indexing. If your site isn&#8217;t enabled for mobile-first indexing yet, you&#8217;ve seen a<br \/>\n  drop in ranking after your site is enabled for mobile-first indexing, or you&#8217;ve received a<br \/>\n  message in Search Console, check the following list of common errors and resolve possible<br \/>\n  errors you may have:\n<\/p>\n<table class=\"properties responsive\">\n<tr>\n<th colspan=\"2\">Errors<\/th>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"missing-structured-data\" tabindex=\"-1\">Missing structured data<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: The mobile page doesn&#8217;t have all the structured<br \/>\n      data markup that the desktop page has.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b>\n      <\/p>\n<ol>\n<li>\n          Verify that the structured data is present on both versions of your site (desktop and<br \/>\n          mobile).\n        <\/li>\n<li>Make sure that your mobile and desktop sites have the same structured data.<\/li>\n<li>\n          Use correct URLs in structured data. Make sure that URLs in the structured data on the<br \/>\n          mobile versions are updated to the correct URLs.\n        <\/li>\n<li>\n          Check extraction errors for your structured data. If you use<br \/>\n          <a href=\"https:\/\/support.google.com\/webmasters\/answer\/2692911\" class=\"external-link\">Data Highlighter<\/a><br \/>\n          to provide structured data, regularly check the<br \/>\n          <a href=\"https:\/\/www.google.com\/webmasters\/tools\/data-highlighter\" class=\"external-link\">Data Highlighter dashboard<\/a><br \/>\n          for extraction errors.\n        <\/li>\n<li>\n          Use the<br \/>\n          <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9012289\" class=\"external-link\">URL Inspection tool<\/a><br \/>\n          to check that the content is visible on the rendered page (the rendered page is how<br \/>\n          Google sees your page).\n        <\/li>\n<\/ol>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"noindex-tag-on-pages\" tabindex=\"-1\"><code>noindex<\/code> tag on pages<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: A mobile page is blocked from indexing by a<br \/>\n      <code>noindex<\/code> tag.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b>:<br \/>\n        Use the same <span>robots<\/span> <code>meta<\/code> tags on the mobile site and the desktop site. Don&#8217;t use the<br \/>\n        <code>noindex<\/code> tag on the mobile page (otherwise, Google won&#8217;t index your page<br \/>\n        when your site is enabled for mobile-first indexing).\n      <\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"missing-image\" tabindex=\"-1\">Missing image<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: The mobile page doesn&#8217;t have all the important<br \/>\n      images that the desktop page has.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b>\n      <\/p>\n<ol>\n<li>\n          Make sure that your mobile site contains the same content as your desktop site. If<br \/>\n          your mobile site has less content than your desktop site, consider updating your<br \/>\n          mobile site so that its primary content is equivalent with your desktop site. Only the<br \/>\n          content shown on the mobile site is used for indexing.\n        <\/li>\n<li>\n          Use the same <span>robots<\/span> <code>meta<\/code> tags on the mobile site and the desktop site. Don&#8217;t use the<br \/>\n          <code>nofollow<\/code> tag on the mobile page (otherwise, Google won&#8217;t crawl and index<br \/>\n          the images on your page when your site is enabled for mobile-first indexing).\n        <\/li>\n<li>\n          Use a<br \/>\n          <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/images-best-practices\/#supported-image-formats\" class=\"external-link\">supported format and tag for images<\/a>.<br \/>\n          For example, Google supports SVG format images, but our systems can&#8217;t index a .jpg<br \/>\n          image in the <code>&lt;image&gt;<\/code> tag inside an inline SVG.\n        <\/li>\n<li>\n          Don&#8217;t lazy-load primary content upon user interaction. Google won&#8217;t load content that<br \/>\n          requires user interactions (for example, swiping, clicking, or typing) to load.<br \/>\n          <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/fix-lazy-loaded-content\/\">Make sure that Google can see lazy-loaded content<\/a>.\n        <\/li>\n<\/ol>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"blocked-image\" tabindex=\"-1\">Blocked image<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: An important image on the mobile page is blocked<br \/>\n      by robots.txt.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b>:<br \/>\n        Let Google crawl your resources. Some images have different URLs on the mobile site from<br \/>\n        those on the desktop site. If you want Google to crawl your URLs, don&#8217;t block the URL<br \/>\n        with the<br \/>\n        <a href=\"https:\/\/developers.google.com\/search\/doc\/crawling-indexing\/robots\/robots_txt#disallow\"><code>disallow<\/code> rule<\/a>.\n      <\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"low-quality-image\" tabindex=\"-1\">Low quality image<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: An important image on the mobile page is too small<br \/>\n      or low resolution.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b>:<br \/>\n        Provide <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/images-best-practices\/#good-quality-photos\">high quality images<\/a>.<br \/>\n        Don&#8217;t use images that are too small or have a low resolution on the mobile site.\n    <\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"missing-alt-text\" tabindex=\"-1\">Missing alt text<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: An important image on the mobile page is missing<br \/>\n      alt text.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b>:<br \/>\n        Use the same<br \/>\n        <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/images-best-practices\/#descriptive-alt-text\">alt text<\/a> for<br \/>\n        images on your mobile site as you do on your desktop site.\n    <\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"missing-page-title\" tabindex=\"-1\">Missing page title<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: A mobile page is missing a title.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b>:<br \/>\n         Make sure that the <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/title-links\/#page-titles\">titles<\/a><br \/>\n         and <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/snippets\/#meta-descriptions\">meta descriptions<\/a><br \/>\n         are equivalent across both versions of your site.\n      <\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"missing-meta-description\" tabindex=\"-1\">Missing meta description<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: A mobile page is missing the meta description.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b>:<br \/>\n        Make sure that the <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/title-links\/#page-titles\">titles<\/a><br \/>\n        and <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/snippets\/#meta-descriptions\">meta descriptions<\/a><br \/>\n        are equivalent across both versions of your site.\n      <\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"mobile-url-on-error-page\" tabindex=\"-1\">Mobile URL is an error page<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: The mobile page is an error page.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b>:<br \/>\n        Make sure error page status is the same across desktop and mobile site. If a page on<br \/>\n        your desktop site serves normal contents and your mobile site&#8217;s version of that page<br \/>\n        serves an error page, this page will be missing from the index.\n    <\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"mobile-url-anchor-fragment\" tabindex=\"-1\">Mobile URL has anchor fragment<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: The mobile URL includes an anchor fragment; Google<br \/>\n      can&#8217;t index URLs that include fragments.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b>:<br \/>\n        Make sure your mobile version doesn&#8217;t have URL fragments. Most of the time, fragment<br \/>\n        URLs are not indexable, and these pages will be missing from the index after your domain<br \/>\n        is enabled for mobile-first indexing.\n      <\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"mobile-page-blocked-robots\" tabindex=\"-1\">Mobile page blocked by robots.txt<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: The mobile page is blocked by a robots.txt rule.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b>:<br \/>\n        Verify that your robots.txt rules and <span>robots<\/span> <code>meta<\/code> tags work as you intended for<br \/>\n        both versions of your site. Use the same robots.txt rules for both mobile and<br \/>\n        desktop versions of your site.\n      <\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"duplicate-mobile-page-target\" tabindex=\"-1\">Duplicate mobile page target<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: Multiple desktop pages redirect to the same mobile<br \/>\n       page.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b>:<br \/>\n        Ensure desktop versions which serve different contents have equivalent mobile versions.<br \/>\n        If different URLs redirects to the same URL, on mobile devices, after your domain is<br \/>\n        enabled for mobile-first indexing, all these pages will be missing from the index.\n      <\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"desktop-redirects-to-mobile\" tabindex=\"-1\">Desktop site redirects to the mobile home page<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: Most or all pages on your desktop site redirect to<br \/>\n      the mobile site&#8217;s home page.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b>:<br \/>\n        Ensure the desktop version has an equivalent mobile version. If different URLs redirect<br \/>\n        to the home page on mobile devices, all these pages will be missing from the index after<br \/>\n        your domain is migrated for mobile-first indexing.\n      <\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"page-quality-issues\" tabindex=\"-1\">Page quality issues<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: The mobile page has issues with ads, missing<br \/>\n      content, titles, or descriptive elements for images on the page.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue:<\/b>\n      <\/p>\n<ol>\n<li>\n          Don&#8217;t let ads harm your mobile page ranking. Follow the<br \/>\n          <a href=\"https:\/\/www.betterads.org\/standards\/\" class=\"external-link\">Better Ads Standard<\/a><br \/>\n          when displaying ads on mobile devices.\n        <\/li>\n<li>\n          Make sure your mobile site contains the same content as your desktop site. If your<br \/>\n          mobile site has less content than your desktop site, consider updating your mobile<br \/>\n          site so that its primary content is equivalent with your desktop site. Only the<br \/>\n          content shown on the mobile site is used for indexing.\n        <\/li>\n<li>\n          Make sure you use the same clear and meaningful headings on the mobile site as you do<br \/>\n          on the desktop site.\n        <\/li>\n<li>\n          Use the same<br \/>\n          <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/images-best-practices\/#descriptive-titles-captions-filenames\">titles, captions, filenames, and text<\/a><br \/>\n          relevant to the images on the mobile site you do for the desktop site.\n        <\/li>\n<\/ol>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"video-issues\" tabindex=\"-1\">Video issues<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: The mobile page has a video that is not in a<br \/>\n      supported format, is placed in a difficult to find location, is missing meta descriptions,<br \/>\n      or is very slow to load.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue:<\/b>\n      <\/p>\n<ol>\n<li>\n          Use a <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/video-search\/#file-types\">supported format<\/a> for your<br \/>\n          videos and put them in supported tags. Videos are identified in the page by the<br \/>\n          presence of an HTML tag, for example: <code>&lt;video&gt;<\/code>,<br \/>\n          <code>&lt;embed&gt;<\/code>, or <code>&lt;object&gt;<\/code>.\n        <\/li>\n<li>\n          Don&#8217;t lazy-load primary content upon user interaction. Google won&#8217;t load content that<br \/>\n          requires user interactions (for example, swiping, clicking or typing) to load.<br \/>\n          <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/fix-lazy-loaded-content\/\">Make sure Google can see lazy-loaded content<\/a>.\n        <\/li>\n<li>\n          Place the video in an easy to find location on your mobile site. For example, it might<br \/>\n          harm the video&#8217;s ranking if users need to scroll down too much to find the video on<br \/>\n          mobile page.\n        <\/li>\n<\/ol>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"hostload-issues\" tabindex=\"-1\">Hostload issues<\/h3>\n<\/td>\n<td>\n      <i class=\"material-icons\" aria-hidden=\"true\">error<\/i><br \/>\n      <b>What caused the issue<\/b>: Some of the hosts don&#8217;t have enough hostload.<\/p>\n<p>\n        <i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b>:<br \/>\n        Ensure that your mobile site has enough capacity to handle a potential increase in<br \/>\n        <a href=\"https:\/\/support.google.com\/webmasters\/answer\/35253\" class=\"external-link\">crawl rate<\/a><br \/>\n        on the mobile version of your site.\n      <\/p>\n<\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"<p>Discover what Google mobile-first indexing is and explore best practices designed to improve user experience in Google Search.<\/p>\n","protected":false},"menu_order":32,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[681],"ar_kb_etiket":[],"class_list":["post-25565","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-crawling-and-indexing"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25565","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":1,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25565\/revisions"}],"predecessor-version":[{"id":25690,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25565\/revisions\/25690"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/27584"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=25565"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=25565"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=25565"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}