Thủ Thuật Hướng dẫn Google mobile on desktop Đầy đủ Chi Tiết
You đang tìm kiếm từ khóa Google mobile on desktop Đầy đủ được Cập Nhật vào lúc : 2022-03-10 10:34:00 . Với phương châm chia sẻ Kinh Nghiệm về trong nội dung bài viết một cách Chi Tiết 2022. Nếu sau khi đọc tài liệu vẫn ko hiểu thì hoàn toàn có thể lại Comments ở cuối bài để Admin lý giải và hướng dẫn lại nha.
Quý khách đang tìm kiếm từ khóa Google mobile on desktop được Cập Nhật vào lúc : 2022-03-10 10:34:08 . Với phương châm chia sẻ Mẹo về trong nội dung nội dung bài viết một cách Chi Tiết Mới Nhất. Nếu sau khi Read tài liệu vẫn ko hiểu thì hoàn toàn hoàn toàn có thể lại phản hồi ở cuối bài để Ad lý giải và hướng dẫn lại nha.
Make sure that Googlebot can access and render your content
Make sure that content is the same on desktop and mobile
Check your structured data
Check the placement of your ads
Check visual content
Check your images
Check your videos
Additional best practices for separate URLs
Troubleshooting
Recent updates
(This post was largely translated from our Japanese version of the Webmaster Central Blog)
Recently I introduced several methods to ensure your mobile site is properly indexed by Google. Today I’d like to share information useful for webmasters who manage both desktop and mobile phone versions of a site.
One of the most common problems for webmasters who run both mobile and desktop versions of a site is that the mobile version of the site appears for users on a desktop computer, or that the desktop version of the site appears when someone finds them from a mobile device. In dealing with this scenario, here are two viable options:
Redirect mobile users to the correct version
When a mobile user or crawler (like Googlebot-Mobile) accesses the desktop version of a URL, you can redirect them to the corresponding mobile version of the same page. Google notices the relationship between the two versions of the URL and displays the standard version for searches from desktops and the mobile version for mobile searches. If you redirect users, please make sure that the content on the corresponding mobile/desktop URL matches as closely as possible. For example, if you run a shopping site and there’s an access from a mobile phone to a desktop-version URL, make sure that the user is redirected to the mobile version of the page for the same product, and not to the homepage of the mobile version of the site. We occasionally find sites using this kind of redirect in an attempt to boost their search rankings, but this practice only results in a negative user experience, and so should be avoided all costs.
On the other hand, when there’s an access to a mobile-version URL from a desktop browser or by our web crawler, Googlebot, it’s not necessary to redirect them to the desktop-version. For instance, Google doesn’t automatically redirect desktop users from their mobile site to their desktop site, instead they include a link on the mobile-version page to the desktop version. These links are especially helpful when a mobile site doesn’t provide the full functionality of the desktop version—users can easily navigate to the desktop-version if they prefer.
Switch content based on User-agent
Some sites have the same URL for both desktop and mobile content, but change their format according to User-agent. In other words, both mobile users and desktop users access the same URL (that is, no redirects), but the content/format changes slightly according to the User-agent. In this case, the same URL will appear for both mobile search and desktop search, and desktop users can see a desktop version of the content while mobile users can see a mobile version of the content.
However, note that if you fail to configure your site correctly, your site could be considered to be cloaking, which can lead to your site disappearing from our search results. Cloaking refers to an attempt to boost search result rankings by serving different content to Googlebot than to regular users. This causes problems such as less relevant results (pages appear in search results even though their content is actually unrelated to what users see/want), so we take cloaking very seriously.
So what does “the page that the user sees” mean if you provide both versions with a URL? As I mentioned in the previous post, Google uses “Googlebot” for web search and “Googlebot-Mobile” for mobile search. To remain within our guidelines, you should serve the same content to Googlebot as a typical desktop user would see, and the same content to Googlebot-Mobile as you would to the browser on a typical mobile device. It’s fine if the contents for Googlebot are different from the one for Googlebot-Mobile.
One example of how you could be unintentionally detected for cloaking is if your site returns a message like “Please access from mobile phones” to desktop browsers, but then returns a full mobile version to both crawlers (so Googlebot receives the mobile version). In this case, the page which web search users see (for example, “Please access from mobile phones”) is different from the page which Googlebot crawls (for example, “Welcome to my site”). Again, we detect cloaking because we want to serve users the same relevant content that Googlebot or Googlebot-Mobile crawled.
Diagram of serving content from your mobile-enabled site
We’re working on a daily basis to improve search results and solve problems, but because the relationship between PC and mobile versions of a web site can be nuanced, we appreciate the cooperation of webmasters. Your help will result in more mobile content being indexed by Google, improving the search results provided to users. Thank you for your cooperation in improving the mobile search user experience.
Posted by Jun Mukai, Software Engineer, Mobile Search Team
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
[ “type”: “thumb-down”, “id”: “missingTheInformationINeed”, “label”:”Missing the information I need” , “type”: “thumb-down”, “id”: “tooComplicatedTooManySteps”, “label”:”Too complicated / too many steps” , “type”: “thumb-down”, “id”: “outOfDate”, “label”:”Out of date” , “type”: “thumb-down”, “id”: “samplesCodeIssue”, “label”:”Samples / code issue” , “type”: “thumb-down”, “id”: “otherDown”, “label”:”Other” ] [ “type”: “thumb-up”, “id”: “easyToUnderstand”, “label”:”Easy to understand” , “type”: “thumb-up”, “id”: “solvedMyProblem”, “label”:”Solved my problem” , “type”: “thumb-up”, “id”: “otherUp”, “label”:”Other” ]
Mobile-first indexing means Google predominantly uses the mobile version of the content for indexing and ranking. Historically, the index primarily used the desktop version of a page’s content when evaluating the relevance of a page to a user’s query. Since the majority of users now access Google Search with a mobile device, Googlebot primarily crawls and indexes pages with the smartphone agent going forward.
While it’s not required to have a mobile version of your pages to have your content included in Google’s Search results, it is very strongly recommended.
Starting July 1, 2022, mobile-first indexing is enabled by default for all new websites (new to the web or previously unknown to Google Search). For older or existing websites, we continue to monitor and evaluate pages based on the best practices detailed in this guide. We inform site owners in Search Console of the date when their site was switched to mobile-first indexing.
It’s important to note that there isn’t a separate mobile-first index; Google Search continues to use only one index. Google Search continues to show the URL that is the most appropriate to users (whether it’s a desktop or mobile URL) in Search results.
To make sure that your users have the best experience, follow the best practices detailed in this guide.
Make sure that Googlebot can access and render your content
Make sure that Googlebot can access and render your mobile page content and resources.
- Use the same meta robots tags on the mobile and desktop site. If you use a different meta robots tag on the mobile site (especially the noindex or nofollow tags), Google may fail to crawl and index your page when your site is enabled for mobile-first indexing.
Don’t lazy-load primary content upon user interaction. Googlebot won’t load content that requires user interactions (for example, swiping, clicking, or typing) to load. Make sure that Google can see lazy-loaded content.
Let Google crawl your resources. Some resources have different URLs on the mobile site from those on the desktop site. If you want Google to crawl your URLs, make sure that you’re not blocking the URL with the disallow directive.
Make sure that content is the same on desktop and mobile
- Make sure that your mobile site contains the same content as your desktop site. If your mobile site has less content than your desktop site, consider updating your mobile site so that its primary content is equivalent to your desktop site. You can have a different design on mobile to maximize user experience (for example, moving content into accordions or tabs); just make sure that the content is equivalent to the desktop site, since almost all indexing on your site comes from the mobile site. WARNING: If it’s your intention that the mobile page should have less content than the desktop page, you can expect some traffic loss when your site is enabled mobile-first indexing, since Google can’t get as much information from your page as before. Instead of removing content, consider moving content into accordions or tabs to save space.
Use the same clear and meaningful headings on the mobile site as you do on the desktop site.
Even with the equivalent content, differences in DOM or layout between desktop and mobile page can result in Google understanding the content differently.
Check your structured data
If you have structured data on your site, make sure that it’s present on both versions of your site. Here are some specific things to check:
- Make sure that your mobile and desktop sites have the same structured data. If you have to prioritize which types you add to your mobile site, start with Breadcrumb, Product, and VideoObject structured data.
Use correct URLs in structured data. Make sure that URLs in the structured data on the mobile versions are updated to the mobile URLs.
If you use Data Highlighter, train it on your mobile site. If you use Data Highlighter to provide structured data, regularly check the Data Highlighter dashboard for extraction errors.
Make sure that the descriptive title and meta description are equivalent across both versions of your site.
Check the placement of your ads
Don’t let ads harm your mobile page ranking. Follow the Better Ads Standard when displaying ads on mobile devices. For example, ads the top of the page can take up too much room on a mobile device, which is a bad user experience
Check visual content
Check your images
Make sure that the images on your mobile site follow the image best practices. In particular, we recommend that you:
- Provide high quality images. Don’t use images that are too small or have a low resolution on the mobile site.
Use a supported format for images. Don’t use unsupported formats or tags. For example, Google supports SVG format images, but our systems can’t index a .jpg image in the tag inside an inline SVG.
Don’t use URLs that change every time the page loads for images. Google won’t be able to process and index your resources properly if you use constantly-changing URLs for them.
Make sure that the mobile site has the same alt text for images as the desktop site. Use descriptive alt text for images on your mobile site as you do on your desktop site.
Make sure that the mobile page content quality is as good as the desktop page. Use the same descriptive titles, captions, filenames, and text relevant to the images on the mobile site as you do for the desktop site.
If your site is using different image URLs for the desktop and mobile site, you may see a temporary image traffic loss while your site transitions to mobile-first indexing. This is because the image URLs on the mobile site are new to Google indexing, and it will take some time for the new image URLs to gain enough historical search results to get a better ranking. To avoid a temporary image traffic loss, use the same image URLs across both versions of your site. If you don’t mind a temporary image traffic loss, you don’t need to take any action.
Check your videos
Make sure that the videos on your mobile site follow the video best practices. In particular, we recommend that you:
- Don’t use URLs that change every time the page loads for your videos. Google won’t be able to process and index your resources properly if you use constantly changing URLs for them.
Use a supported format for your videos and put videos in supported tags. Videos are identified in the page by the presence of an HTML tag, for example:
Additional best practices for separate URLs
If your site has separate URLs for the desktop and mobile versions of a page (also known as m-dot), we recommend the following additional best practices:
- Make sure that the error page status is the same on both the desktop and mobile sites. If a page on your desktop site serves normal contents and your mobile site’s version of that page serves an error page, this page will be missing from the index.
Make sure that your mobile version doesn’t have fragment URLs. The fragment part of the URL is the end of the URL that starts with #. Most of the time, fragment URLs are not indexable, these pages will be missing from the index after your domain is enabled for mobile-first indexing.
Ensure that the desktop versions that serve different contents have equivalent mobile versions. If different URLs redirects to the same URL, for example, homepage, on mobile devices, after your domain is enabled for mobile-first indexing, all these pages will be missing from the index.
Verify both versions of your site in Search Console to make sure that you have access to data and messages for both versions. Your site may experience a data shift when Google switches to mobile-first indexing for your site.
Check hreflang links on separate URLs. When you use rel=hreflang link elements for internationalization, link between mobile and desktop URLs separately. Your mobile URLs’ hreflang should point to mobile URLs, and similarly desktop URL hreflang should point to desktop URLs.
Here’s an example of hreflang for the homepage of a site with separate URLs for mobile and desktop.
In this example, the mobile site URL is ://m.example/.
In this example, the desktop site URL is ://example/.
Ensure that your mobile site has enough capacity to handle a potential increase in crawl rate on the mobile version of your site.
Verify that your robots.txt directives work as you intend for both versions of your site. The robots.txt file lets you specify which parts of a website may be crawled or not. In most cases, use the same robots.txt directives for both mobile and desktop versions of your site.
Use the correct rel=canonical and rel=alternate link elements between your mobile and desktop versions.
Here’s an example of rel=canonical and rel=alternate for a separate URLs site setup.
In this example, the mobile site URL is ://m.example/.
In this example, the desktop site URL is ://example/.
Troubleshooting
Here’s a list of the most common errors that can stop sites from being enabled for mobile-first indexing or could cause a drop in ranking after a site is enabled for mobile-first indexing. If your site isn’t enabled for mobile-first indexing yet, you’ve seen a drop in ranking after your site is enabled for mobile-first indexing, or you’ve received a message in Search Console, check the list of common errors and resolve possible errors you may have.
Errors error What caused the issue: The mobile page doesn’t have all the structured data markup that the desktop page has.
done Fix the issue
Verify that the structured data is present on both versions of your site (desktop and mobile).
Make sure that your mobile and desktop sites have the same structured data.
Use correct URLs in structured data. Make sure that URLs in the structured data on the mobile versions are updated to the correct URLs.
Check extraction errors for your structured data. If you use Data Highlighter to provide structured data, regularly check the Data Highlighter dashboard for extraction errors.
Use the URL Inspection tool to check that the content is visible on the rendered page (the rendered page is how Googlebot sees your page).
error What caused the issue: A mobile page is blocked from indexing by a noindex tag.
done Fix the issue: Use the same meta robots tags on the mobile site and the desktop site. Don’t use the noindex tag on the mobile page (otherwise, Google won’t index your page when your site is enabled for mobile-first indexing).
error What caused the issue: The mobile page doesn’t have all the important images that the desktop page has.
done Fix the issue
Make sure that your mobile site contains the same content as your desktop site. If your mobile site has less content than your desktop site, consider updating your mobile site so that its primary content is equivalent with your desktop site. Only the content shown on the mobile site is used for indexing.
Use the same meta robots tags on the mobile site and the desktop site. Don’t use the nofollow tag on the mobile page (otherwise, Google won’t crawl and index the images on your page when your site is enabled for for mobile-first indexing).
Use a supported format and tag for images. For example, Google supports SVG format images, but our systems can’t index a .jpg image in the tag inside an inline SVG.
Don’t lazy-load primary content upon user interaction. Googlebot won’t load content that requires user interactions (for example, swiping, clicking, or typing) to load. Make sure that Google can see lazy-loaded content.
error What caused the issue: An important image on the mobile page is blocked by robots.txt.
done Fix the issue: Let Google crawl your resources. Some images have different URLs on the mobile site from those on the desktop site. If you want Google to crawl your URLs, don’t block the URL with the disallow directive.
error What caused the issue: An important image on the mobile page is too small or low resolution.
done Fix the issue: Provide high quality images. Don’t use images that are too small or have a low resolution on the mobile site.
error What caused the issue: An important image on the mobile page is missing alt text.
done Fix the issue: Use the same descriptive alt text for images on your mobile site as you do on your desktop site.
error What caused the issue: A mobile page is missing a title.
done Fix the issue: Make sure that the titles and meta descriptions are equivalent across both versions of your site.
error What caused the issue: A mobile page is missing the meta description.
done Fix the issue: Make sure that the titles and meta descriptions are equivalent across both versions of your site.
error What caused the issue: The mobile page is an error page.
done Fix the issue: Make sure error page status is the same across desktop and mobile site. If a page on your desktop site serves normal contents and your mobile site’s version of that page serves an error page, this page will be missing from the index.
error What caused the issue: The mobile URL includes an anchor fragment; Google can’t index URLs that include fragments.
done Fix the issue: Make sure your mobile version doesn’t have fragment URLs. Most of the time, fragment URLs are not indexable, and these pages will be missing from the index after your domain is enabled for for mobile-first indexing.
error What caused the issue: The mobile page is blocked by a robots.txt rule.
done Fix the issue: Verify that your robots.txt directives and robots meta tags work as you intended for both versions of your site. Use the same robots.txt directives for both mobile and desktop versions of your site.
error What caused the issue: Multiple desktop pages redirect to the same mobile page.
done Fix the issue: Ensure desktop versions which serve different contents have equivalent mobile versions. If different URLs redirects to the same URL, on mobile devices, after your domain is enabled for mobile-first indexing, all these pages will be missing from the index.
error What caused the issue: Most or all pages on your desktop site redirect to the mobile site’s homepage.
done Fix the issue: Ensure the desktop version has an equivalent mobile version. If different URLs redirect to the homepage on mobile devices, all these pages will be missing from the index after your domain is migrated for mobile-first indexing.
error What caused the issue: The mobile page has issues with ads, missing content, titles, or descriptive elements for images on the page.
done Fix the issue
Don’t let ads harm your mobile page ranking. Follow the Better Ads Standard when displaying ads on mobile devices.
Make sure your mobile site contains the same content as your desktop site. If your mobile site has less content than your desktop site, consider updating your mobile site so that its primary content is equivalent with your desktop site. Only the content shown on the mobile site is used for indexing.
Make sure you use the same clear and meaningful headings on the mobile site as you do on the desktop site.
Use the same descriptive titles, captions, filenames, and text relevant to the images on the mobile site you do for the desktop site.
error What caused the issue: The mobile page has a video that is not in a supported format, is placed in a difficult to find location, is missing meta descriptions, or is very slow to load.
done Fix the issue
Use a supported format for your videos and put them in supported tags. Videos are identified in the page by the presence of an HTML tag, for example:
error What caused the issue: Some of the hosts don’t have enough hostload.
done Fix the issue: Ensure that your mobile site has enough capacity to handle a potential increase in crawl rate on the mobile version of your site.
Recent updates
We’ve announced a lot of updates around mobile-first indexing. Here’s a log of everything we’ve announced on the Google Search Central blog:
UpdatesMarch 4, 2022 Mobile-first indexing will be enabled for all websites starting September 2022. In the meantime, we’ll continue moving sites to mobile-first indexing when our systems recognize that they’re ready. May 28, 2022 Mobile-first indexing is enabled by default for all new, previously unknown to Google Search, websites starting July 1, 2022. For older sites, we’ll continue to monitor and evaluate pages for readiness, and will notify site owners through Search Console once they’re ready. December 19, 2022 We notify the site owner through Search Console when we move the site to mobile-first indexing. Prepare for mobile-first indexing by verifying that structured data and alt-attributes are on both versions of your pages. March 26, 2022 Mobile-first indexing is rolling out more broadly. We published documentation on how to prepare for mobile-first indexing. Content gathered by mobile-first indexing has no ranking advantage over mobile content that’s not yet gathered this way or desktop content. December 18, 2022 We will be evaluating sites for readiness and cautiously rolling out mobile-first indexing for sites that are ready. November 4, 2022 We are experimenting with making the index mobile-first.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2022-11-22 UTC.
[ “type”: “thumb-down”, “id”: “missingTheInformationINeed”, “label”:”Missing the information I need” , “type”: “thumb-down”, “id”: “tooComplicatedTooManySteps”, “label”:”Too complicated / too many steps” , “type”: “thumb-down”, “id”: “outOfDate”, “label”:”Out of date” , “type”: “thumb-down”, “id”: “samplesCodeIssue”, “label”:”Samples / code issue” , “type”: “thumb-down”, “id”: “otherDown”, “label”:”Other” ] [ “type”: “thumb-up”, “id”: “easyToUnderstand”, “label”:”Easy to understand” , “type”: “thumb-up”, “id”: “solvedMyProblem”, “label”:”Solved my problem” , “type”: “thumb-up”, “id”: “otherUp”, “label”:”Other” ]
Chia Sẻ Link Tải Google mobile on desktop miễn phí
Bạn vừa Read tài liệu Với Một số hướng dẫn một cách rõ ràng hơn về Video Google mobile on desktop tiên tiến và phát triển và tăng trưởng nhất và ShareLink Download Google mobile on desktop miễn phí.
Giải đáp vướng mắc về Google mobile on desktop
Nếu sau khi đọc nội dung nội dung bài viết Google mobile on desktop vẫn chưa hiểu thì hoàn toàn hoàn toàn có thể lại Comments ở cuối bài để Tác giả lý giải và hướng dẫn lại nha
#Google #mobile #desktop
Clip Google mobile on desktop Đầy đủ ?
Bạn vừa tìm hiểu thêm Post Với Một số hướng dẫn một cách rõ ràng hơn về Review Google mobile on desktop Đầy đủ tiên tiến và phát triển nhất
Người Hùng đang tìm một số trong những Share Link Cập nhật Google mobile on desktop Đầy đủ Free.
Hỏi đáp vướng mắc về Google mobile on desktop Đầy đủ
Nếu sau khi đọc nội dung bài viết Google mobile on desktop Đầy đủ vẫn chưa hiểu thì hoàn toàn có thể lại Comments ở cuối bài để Mình lý giải và hướng dẫn lại nha
#Google #mobile #desktop #Đầy #đủ