#(examplepage)

[beargraphs]

Character Page // Free Code

[ dark ] | [ light ] [ d.preview ] | [ l.preview ]

a free-to-use character page; applied by using the 'custom html' option after creating a new page - the code can be edited to adjust colours, fonts etc. recommended for use by those with some experience editing basic code as all adjustments (pictures, text etc) are managed within the code. any questions - never hesitate to shoot me a message :)

[mite-rva]

Nginx

참고: https://smali-kazmi.medium.com/setup-nginx-node-js-on-mac-os-x-b31eda9f7d5d

how to read (pronounce): 엔진 엑스

Nginx currently supports 7 scripting languages: Go, Node.js, Perl, PHP, Python, Ruby, and Java Servlet Containers

(the last is an experimental module)

It enables you to run applications written in different languages on the same server.

how to install: https://dev.to/logrocket/how-to-run-a-node-js-server-with-nginx-588

how to install by M2: 1. homebrew install with terminal commands

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

2. PATH for homebrew: (2-lines)

(echo; echo 'eval "$(/opt/homebrew/bin/brew shellenv)"') >> /Users/nika/.zprofile

eval "$(/opt/homebrew/bin/brew shellenv)"

3. run:

To start nginx now and restart at login:

  brew services start nginx

Or, if you don't want/need a background service you can just run:

  /opt/homebrew/opt/nginx/bin/nginx -g daemon\ off\;

[like this] nginx, "http://localhost:8080/"

4. stop

nginx -s stop

5. 에러 확인:

 nginx -t

nginx: the configuration file /opt/homebrew/etc/nginx/nginx.conf syntax is ok

nginx: configuration file /opt/homebrew/etc/nginx/nginx.conf test is successful

6. 리로드:

nginx -s reload

sudo nano /opt/homebrew/etc/nginx/nginx.conf (after password)

디폴트 구성 바꾸기, (nano: vim, emacs 같은 에디터로 수정하게끔 슈퍼유저 설정 권한을 준다)

나노 명령어:

^G : 도움말 보기

^X : 끝내기

^O : 파일 저장(저장할 파일명 입력, 디폴트는 최초 파일명)

^R : 파일 읽기(현재 파일에 새로운 파일 추가)

^W : 텍스트 검색

^\ : 검색 후 바꾸기

^K : 선택한 문자열 잘라내기

^U : 잘라낸 문자열 붙이기

^J : 양쪽 정렬(한줄로 표시)

^T : 맞춤법 체크

^C : 현재 커서 위치

^- : 입력한 행번호, 열번호로 이동

^A : 현재 행의 처음으로 이동

^E : 현재 행의 마지막으로 이동

Mac 폴더 생성 명령어: mkdir servers

mkdir -p /var/www/sena.com

Mac 파일 생성 명령어: touch ~/servers/examplePage/example.com (~ kite까지 포함)

touch ~/servers/examplePage/app.js

nano 안 쓰고 에러 해결법:

sudo vi 만드려는 파일명 or 저장 할 때 

:w !sudo tee % > /dev/null

the page eXample:

make folder and "example.com" file

make app.js (javaScript file)

edit /etc/hosts (add 127.0.0.1 example.com)

새 포트 추가하는 법:

이걸 하고 싶으면 이러면 된다: sudo nano /opt/homebrew/etc/nginx/nginx.conf

링크

[seo53703]

What you Need to Know about Google’s Mobile-First Indexing Rollout

What you Need to Know about Google’s Mobile-First Indexing Rollout

Anyone reading this has probably already heard the news: Google announced last week that they’re “migrating sites that follow the best practices for mobile-first indexing.” Anyone who keeps abreast of SEO news (or works with clients who do) has probably received an email since that announcement wondering nervously what this means for their site.

Worry not!! This update to Google’s indexing process is not likely to affect your site or your clients’ sites, especially if you’re already following best practices for mobile friendliness. Unless you serve noticeably different content to mobile users than you do to desktop users, the mobile-first index should not change your rankings.

What exactly did Google announce?

This is not the first time Google has talked about mobile-first indexing. In November 2016, they announced that they’d “begun experiments to make [their] index mobile-first.” Now, the mobile-first index is being rolled out “more broadly”, starting with “sites that follow the best practices.”

The mobile-first index is not a separate Google index. Rather, Google will be replacing desktop versions of pages in its index with their mobile counterparts.

If a site you work on has been chosen as one of the lucky ones, you should have received a notification in Google Search Console with the subject line “Mobile-first indexing enabled for www.yoursite.com.” If you haven’t received a notification, I would not assume that your site isn’t being moved to the mobile-first index. As is often the case with Search Console, the absence of information doesn’t tell you much.

Who is NOT affected by mobile-first indexing?

The Google Developer post about the mobile-first index (updated this week) very clearly outlines what kinds of sites will or will not be affected by this update.

This table from that post shows some of the most crucial information about the mobile-first indexing update.

Let’s break it down.

Your Site is Desktop Only

If your site is designed only for desktop users and does not change when a user is on a mobile device, mobile-first indexing will not affect you. That said, you should definitely tailor your site experience for mobile users if you care about SEO, since a growing majority of searches happen on mobile devices (and the data in this post is from 2016)!

Your Site is Responsive

A site using responsive design based on the viewport will not be affected by mobile-first indexing. This is because the “mobile version” of the site has the same content and code as the desktop version, so the indexed content will not change.

Your Site Exists Entirely in AMP

Good for you! If the only version of your site is built in AMP, your site is essentially already in the “mobile-first index”, because your site is streamlined for mobile users.

Who IS affected by mobile-first indexing? Your Site has Separate URLs for Mobile and Desktop Content

If your mobile site exists on a separate subdomain (such as m.yoursite.com), or you serve up mobile URLs in place of desktop URLs (yoursite.com/examplepage/mobile), mobile-first indexing WILL affect you. Google will start to index the mobile pages preferentially over the desktop pages

Your Site Dynamically Serves Content based on User Device

Similar to the scenario above, if your site is changing the content that a page delivers based on the device a user is on, the mobile versions of your pages will be going into the mobile-first index. The main difference between this and the Separate URLs scenario above is that your mobile content is not on a different URL or subdomain.

A quick note on these two cases, which could really be a separate blog post: We SEO talking-heads at Portent generally advise against separate URLs/different content for mobile users. Google Best Practices require you to deliver the same content on both versions of your pages. If you fail to do this, you could get flagged and penalized for cloaking, which is bad-news-bears. If at all possible, go with responsive design.

Your Site has AMP Versions of non-AMP Pages

This stands out to me as the most interesting part. If your site has AMP and non-AMP pages, “Google prefers the mobile version of the non-AMP URL for indexing.” In other words, mobile-first indexing will ignore your AMP pages and index regular versions of pages in their mobile forms. If you rely on AMP for your mobile experience, check to make sure your non-AMP pages work well on mobile devices.

Other Takeaways on Mobile-First Indexing

Everything in this post is contingent on whether you believe what Google says to be “true.” There’s nothing in the rulebook (nor in their track record) that says Google has to be 100% forthcoming, so take it all with a grain (or shaker) of salt.

The Official Google Webmaster post reinforces what we already know, but it’s good to hear it again: making a site mobile-friendly will help it perform better in mobile search results. A critically important example: fast-loading content helps a site perform better for users, and will perform better in organic search than slow-loading content after the update in July 2018.

We said it above, but it bears repeating: inclusion in the mobile-first index does not inherently mean you will rank higher.

This is all very new and exciting stuff, and I’m looking forward to hearing your thoughts. Have any of your clients received the Search Console notification that they’re being included? Have you seen any changes in how your site shows up in Google search?

https://ift.tt/2uIOBxn

[piatty29033]

What you Need to Know about Google’s Mobile-First Indexing Rollout

What you Need to Know about Google’s Mobile-First Indexing Rollout

Anyone reading this has probably already heard the news: Google announced last week that they’re “migrating sites that follow the best practices for mobile-first indexing.” Anyone who keeps abreast of SEO news (or works with clients who do) has probably received an email since that announcement wondering nervously what this means for their site.

Worry not!! This update to Google’s indexing process is not likely to affect your site or your clients’ sites, especially if you’re already following best practices for mobile friendliness. Unless you serve noticeably different content to mobile users than you do to desktop users, the mobile-first index should not change your rankings.

What exactly did Google announce?

This is not the first time Google has talked about mobile-first indexing. In November 2016, they announced that they’d “begun experiments to make [their] index mobile-first.” Now, the mobile-first index is being rolled out “more broadly”, starting with “sites that follow the best practices.”

The mobile-first index is not a separate Google index. Rather, Google will be replacing desktop versions of pages in its index with their mobile counterparts.

If a site you work on has been chosen as one of the lucky ones, you should have received a notification in Google Search Console with the subject line “Mobile-first indexing enabled for www.yoursite.com.” If you haven’t received a notification, I would not assume that your site isn’t being moved to the mobile-first index. As is often the case with Search Console, the absence of information doesn’t tell you much.

Who is NOT affected by mobile-first indexing?

The Google Developer post about the mobile-first index (updated this week) very clearly outlines what kinds of sites will or will not be affected by this update.

This table from that post shows some of the most crucial information about the mobile-first indexing update.

Let’s break it down.

Your Site is Desktop Only

If your site is designed only for desktop users and does not change when a user is on a mobile device, mobile-first indexing will not affect you. That said, you should definitely tailor your site experience for mobile users if you care about SEO, since a growing majority of searches happen on mobile devices (and the data in this post is from 2016)!

Your Site is Responsive

A site using responsive design based on the viewport will not be affected by mobile-first indexing. This is because the “mobile version” of the site has the same content and code as the desktop version, so the indexed content will not change.

Your Site Exists Entirely in AMP

Good for you! If the only version of your site is built in AMP, your site is essentially already in the “mobile-first index”, because your site is streamlined for mobile users.

Who IS affected by mobile-first indexing? Your Site has Separate URLs for Mobile and Desktop Content

If your mobile site exists on a separate subdomain (such as m.yoursite.com), or you serve up mobile URLs in place of desktop URLs (yoursite.com/examplepage/mobile), mobile-first indexing WILL affect you. Google will start to index the mobile pages preferentially over the desktop pages

Your Site Dynamically Serves Content based on User Device

Similar to the scenario above, if your site is changing the content that a page delivers based on the device a user is on, the mobile versions of your pages will be going into the mobile-first index. The main difference between this and the Separate URLs scenario above is that your mobile content is not on a different URL or subdomain.

A quick note on these two cases, which could really be a separate blog post: We SEO talking-heads at Portent generally advise against separate URLs/different content for mobile users. Google Best Practices require you to deliver the same content on both versions of your pages. If you fail to do this, you could get flagged and penalized for cloaking, which is bad-news-bears. If at all possible, go with responsive design.

Your Site has AMP Versions of non-AMP Pages

This stands out to me as the most interesting part. If your site has AMP and non-AMP pages, “Google prefers the mobile version of the non-AMP URL for indexing.” In other words, mobile-first indexing will ignore your AMP pages and index regular versions of pages in their mobile forms. If you rely on AMP for your mobile experience, check to make sure your non-AMP pages work well on mobile devices.

Other Takeaways on Mobile-First Indexing

Everything in this post is contingent on whether you believe what Google says to be “true.” There’s nothing in the rulebook (nor in their track record) that says Google has to be 100% forthcoming, so take it all with a grain (or shaker) of salt.

The Official Google Webmaster post reinforces what we already know, but it’s good to hear it again: making a site mobile-friendly will help it perform better in mobile search results. A critically important example: fast-loading content helps a site perform better for users, and will perform better in organic search than slow-loading content after the update in July 2018.

We said it above, but it bears repeating: inclusion in the mobile-first index does not inherently mean you will rank higher.

This is all very new and exciting stuff, and I’m looking forward to hearing your thoughts. Have any of your clients received the Search Console notification that they’re being included? Have you seen any changes in how your site shows up in Google search?

https://ift.tt/2uIOBxn

[seo75074]

What you Need to Know about Google’s Mobile-First Indexing Rollout

What you Need to Know about Google’s Mobile-First Indexing Rollout

Anyone reading this has probably already heard the news: Google announced last week that they’re “migrating sites that follow the best practices for mobile-first indexing.” Anyone who keeps abreast of SEO news (or works with clients who do) has probably received an email since that announcement wondering nervously what this means for their site.

Worry not!! This update to Google’s indexing process is not likely to affect your site or your clients’ sites, especially if you’re already following best practices for mobile friendliness. Unless you serve noticeably different content to mobile users than you do to desktop users, the mobile-first index should not change your rankings.

What exactly did Google announce?

This is not the first time Google has talked about mobile-first indexing. In November 2016, they announced that they’d “begun experiments to make [their] index mobile-first.” Now, the mobile-first index is being rolled out “more broadly”, starting with “sites that follow the best practices.”

The mobile-first index is not a separate Google index. Rather, Google will be replacing desktop versions of pages in its index with their mobile counterparts.

If a site you work on has been chosen as one of the lucky ones, you should have received a notification in Google Search Console with the subject line “Mobile-first indexing enabled for www.yoursite.com.” If you haven’t received a notification, I would not assume that your site isn’t being moved to the mobile-first index. As is often the case with Search Console, the absence of information doesn’t tell you much.

Who is NOT affected by mobile-first indexing?

The Google Developer post about the mobile-first index (updated this week) very clearly outlines what kinds of sites will or will not be affected by this update.

This table from that post shows some of the most crucial information about the mobile-first indexing update.

Let’s break it down.

Your Site is Desktop Only

If your site is designed only for desktop users and does not change when a user is on a mobile device, mobile-first indexing will not affect you. That said, you should definitely tailor your site experience for mobile users if you care about SEO, since a growing majority of searches happen on mobile devices (and the data in this post is from 2016)!

Your Site is Responsive

A site using responsive design based on the viewport will not be affected by mobile-first indexing. This is because the “mobile version” of the site has the same content and code as the desktop version, so the indexed content will not change.

Your Site Exists Entirely in AMP

Good for you! If the only version of your site is built in AMP, your site is essentially already in the “mobile-first index”, because your site is streamlined for mobile users.

Who IS affected by mobile-first indexing? Your Site has Separate URLs for Mobile and Desktop Content

If your mobile site exists on a separate subdomain (such as m.yoursite.com), or you serve up mobile URLs in place of desktop URLs (yoursite.com/examplepage/mobile), mobile-first indexing WILL affect you. Google will start to index the mobile pages preferentially over the desktop pages

Your Site Dynamically Serves Content based on User Device

Similar to the scenario above, if your site is changing the content that a page delivers based on the device a user is on, the mobile versions of your pages will be going into the mobile-first index. The main difference between this and the Separate URLs scenario above is that your mobile content is not on a different URL or subdomain.

A quick note on these two cases, which could really be a separate blog post: We SEO talking-heads at Portent generally advise against separate URLs/different content for mobile users. Google Best Practices require you to deliver the same content on both versions of your pages. If you fail to do this, you could get flagged and penalized for cloaking, which is bad-news-bears. If at all possible, go with responsive design.

Your Site has AMP Versions of non-AMP Pages

This stands out to me as the most interesting part. If your site has AMP and non-AMP pages, “Google prefers the mobile version of the non-AMP URL for indexing.” In other words, mobile-first indexing will ignore your AMP pages and index regular versions of pages in their mobile forms. If you rely on AMP for your mobile experience, check to make sure your non-AMP pages work well on mobile devices.

Other Takeaways on Mobile-First Indexing

Everything in this post is contingent on whether you believe what Google says to be “true.” There’s nothing in the rulebook (nor in their track record) that says Google has to be 100% forthcoming, so take it all with a grain (or shaker) of salt.

The Official Google Webmaster post reinforces what we already know, but it’s good to hear it again: making a site mobile-friendly will help it perform better in mobile search results. A critically important example: fast-loading content helps a site perform better for users, and will perform better in organic search than slow-loading content after the update in July 2018.

We said it above, but it bears repeating: inclusion in the mobile-first index does not inherently mean you will rank higher.

This is all very new and exciting stuff, and I’m looking forward to hearing your thoughts. Have any of your clients received the Search Console notification that they’re being included? Have you seen any changes in how your site shows up in Google search?

https://ift.tt/2uIOBxn

[seocompany35203]

What you Need to Know about Google’s Mobile-First Indexing Rollout

What you Need to Know about Google’s Mobile-First Indexing Rollout

Anyone reading this has probably already heard the news: Google announced last week that they’re “migrating sites that follow the best practices for mobile-first indexing.” Anyone who keeps abreast of SEO news (or works with clients who do) has probably received an email since that announcement wondering nervously what this means for their site.

Worry not!! This update to Google’s indexing process is not likely to affect your site or your clients’ sites, especially if you’re already following best practices for mobile friendliness. Unless you serve noticeably different content to mobile users than you do to desktop users, the mobile-first index should not change your rankings.

What exactly did Google announce?

This is not the first time Google has talked about mobile-first indexing. In November 2016, they announced that they’d “begun experiments to make [their] index mobile-first.” Now, the mobile-first index is being rolled out “more broadly”, starting with “sites that follow the best practices.”

The mobile-first index is not a separate Google index. Rather, Google will be replacing desktop versions of pages in its index with their mobile counterparts.

If a site you work on has been chosen as one of the lucky ones, you should have received a notification in Google Search Console with the subject line “Mobile-first indexing enabled for www.yoursite.com.” If you haven’t received a notification, I would not assume that your site isn’t being moved to the mobile-first index. As is often the case with Search Console, the absence of information doesn’t tell you much.

Who is NOT affected by mobile-first indexing?

The Google Developer post about the mobile-first index (updated this week) very clearly outlines what kinds of sites will or will not be affected by this update.

This table from that post shows some of the most crucial information about the mobile-first indexing update.

Let’s break it down.

Your Site is Desktop Only

If your site is designed only for desktop users and does not change when a user is on a mobile device, mobile-first indexing will not affect you. That said, you should definitely tailor your site experience for mobile users if you care about SEO, since a growing majority of searches happen on mobile devices (and the data in this post is from 2016)!

Your Site is Responsive

A site using responsive design based on the viewport will not be affected by mobile-first indexing. This is because the “mobile version” of the site has the same content and code as the desktop version, so the indexed content will not change.

Your Site Exists Entirely in AMP

Good for you! If the only version of your site is built in AMP, your site is essentially already in the “mobile-first index”, because your site is streamlined for mobile users.

Who IS affected by mobile-first indexing? Your Site has Separate URLs for Mobile and Desktop Content

If your mobile site exists on a separate subdomain (such as m.yoursite.com), or you serve up mobile URLs in place of desktop URLs (yoursite.com/examplepage/mobile), mobile-first indexing WILL affect you. Google will start to index the mobile pages preferentially over the desktop pages

Your Site Dynamically Serves Content based on User Device

Similar to the scenario above, if your site is changing the content that a page delivers based on the device a user is on, the mobile versions of your pages will be going into the mobile-first index. The main difference between this and the Separate URLs scenario above is that your mobile content is not on a different URL or subdomain.

A quick note on these two cases, which could really be a separate blog post: We SEO talking-heads at Portent generally advise against separate URLs/different content for mobile users. Google Best Practices require you to deliver the same content on both versions of your pages. If you fail to do this, you could get flagged and penalized for cloaking, which is bad-news-bears. If at all possible, go with responsive design.

Your Site has AMP Versions of non-AMP Pages

This stands out to me as the most interesting part. If your site has AMP and non-AMP pages, “Google prefers the mobile version of the non-AMP URL for indexing.” In other words, mobile-first indexing will ignore your AMP pages and index regular versions of pages in their mobile forms. If you rely on AMP for your mobile experience, check to make sure your non-AMP pages work well on mobile devices.

Other Takeaways on Mobile-First Indexing

Everything in this post is contingent on whether you believe what Google says to be “true.” There’s nothing in the rulebook (nor in their track record) that says Google has to be 100% forthcoming, so take it all with a grain (or shaker) of salt.

The Official Google Webmaster post reinforces what we already know, but it’s good to hear it again: making a site mobile-friendly will help it perform better in mobile search results. A critically important example: fast-loading content helps a site perform better for users, and will perform better in organic search than slow-loading content after the update in July 2018.

We said it above, but it bears repeating: inclusion in the mobile-first index does not inherently mean you will rank higher.

This is all very new and exciting stuff, and I’m looking forward to hearing your thoughts. Have any of your clients received the Search Console notification that they’re being included? Have you seen any changes in how your site shows up in Google search?

https://ift.tt/2uIOBxn

[realestate63141]

What you Need to Know about Google’s Mobile-First Indexing Rollout

What you Need to Know about Google’s Mobile-First Indexing Rollout

Anyone reading this has probably already heard the news: Google announced last week that they’re “migrating sites that follow the best practices for mobile-first indexing.” Anyone who keeps abreast of SEO news (or works with clients who do) has probably received an email since that announcement wondering nervously what this means for their site.

Worry not!! This update to Google’s indexing process is not likely to affect your site or your clients’ sites, especially if you’re already following best practices for mobile friendliness. Unless you serve noticeably different content to mobile users than you do to desktop users, the mobile-first index should not change your rankings.

What exactly did Google announce?

This is not the first time Google has talked about mobile-first indexing. In November 2016, they announced that they’d “begun experiments to make [their] index mobile-first.” Now, the mobile-first index is being rolled out “more broadly”, starting with “sites that follow the best practices.”

The mobile-first index is not a separate Google index. Rather, Google will be replacing desktop versions of pages in its index with their mobile counterparts.

If a site you work on has been chosen as one of the lucky ones, you should have received a notification in Google Search Console with the subject line “Mobile-first indexing enabled for www.yoursite.com.” If you haven’t received a notification, I would not assume that your site isn’t being moved to the mobile-first index. As is often the case with Search Console, the absence of information doesn’t tell you much.

Who is NOT affected by mobile-first indexing?

The Google Developer post about the mobile-first index (updated this week) very clearly outlines what kinds of sites will or will not be affected by this update.

This table from that post shows some of the most crucial information about the mobile-first indexing update.

Let’s break it down.

Your Site is Desktop Only

If your site is designed only for desktop users and does not change when a user is on a mobile device, mobile-first indexing will not affect you. That said, you should definitely tailor your site experience for mobile users if you care about SEO, since a growing majority of searches happen on mobile devices (and the data in this post is from 2016)!

Your Site is Responsive

A site using responsive design based on the viewport will not be affected by mobile-first indexing. This is because the “mobile version” of the site has the same content and code as the desktop version, so the indexed content will not change.

Your Site Exists Entirely in AMP

Good for you! If the only version of your site is built in AMP, your site is essentially already in the “mobile-first index”, because your site is streamlined for mobile users.

Who IS affected by mobile-first indexing? Your Site has Separate URLs for Mobile and Desktop Content

If your mobile site exists on a separate subdomain (such as m.yoursite.com), or you serve up mobile URLs in place of desktop URLs (yoursite.com/examplepage/mobile), mobile-first indexing WILL affect you. Google will start to index the mobile pages preferentially over the desktop pages

Your Site Dynamically Serves Content based on User Device

Similar to the scenario above, if your site is changing the content that a page delivers based on the device a user is on, the mobile versions of your pages will be going into the mobile-first index. The main difference between this and the Separate URLs scenario above is that your mobile content is not on a different URL or subdomain.

A quick note on these two cases, which could really be a separate blog post: We SEO talking-heads at Portent generally advise against separate URLs/different content for mobile users. Google Best Practices require you to deliver the same content on both versions of your pages. If you fail to do this, you could get flagged and penalized for cloaking, which is bad-news-bears. If at all possible, go with responsive design.

Your Site has AMP Versions of non-AMP Pages

This stands out to me as the most interesting part. If your site has AMP and non-AMP pages, “Google prefers the mobile version of the non-AMP URL for indexing.” In other words, mobile-first indexing will ignore your AMP pages and index regular versions of pages in their mobile forms. If you rely on AMP for your mobile experience, check to make sure your non-AMP pages work well on mobile devices.

Other Takeaways on Mobile-First Indexing

Everything in this post is contingent on whether you believe what Google says to be “true.” There’s nothing in the rulebook (nor in their track record) that says Google has to be 100% forthcoming, so take it all with a grain (or shaker) of salt.

The Official Google Webmaster post reinforces what we already know, but it’s good to hear it again: making a site mobile-friendly will help it perform better in mobile search results. A critically important example: fast-loading content helps a site perform better for users, and will perform better in organic search than slow-loading content after the update in July 2018.

We said it above, but it bears repeating: inclusion in the mobile-first index does not inherently mean you will rank higher.

This is all very new and exciting stuff, and I’m looking forward to hearing your thoughts. Have any of your clients received the Search Console notification that they’re being included? Have you seen any changes in how your site shows up in Google search?

https://ift.tt/2uIOBxn

[personalinjurylawyer93555]

What you Need to Know about Google’s Mobile-First Indexing Rollout

What you Need to Know about Google’s Mobile-First Indexing Rollout

Anyone reading this has probably already heard the news: Google announced last week that they’re “migrating sites that follow the best practices for mobile-first indexing.” Anyone who keeps abreast of SEO news (or works with clients who do) has probably received an email since that announcement wondering nervously what this means for their site.

Worry not!! This update to Google’s indexing process is not likely to affect your site or your clients’ sites, especially if you’re already following best practices for mobile friendliness. Unless you serve noticeably different content to mobile users than you do to desktop users, the mobile-first index should not change your rankings.

What exactly did Google announce?

This is not the first time Google has talked about mobile-first indexing. In November 2016, they announced that they’d “begun experiments to make [their] index mobile-first.” Now, the mobile-first index is being rolled out “more broadly”, starting with “sites that follow the best practices.”

The mobile-first index is not a separate Google index. Rather, Google will be replacing desktop versions of pages in its index with their mobile counterparts.

If a site you work on has been chosen as one of the lucky ones, you should have received a notification in Google Search Console with the subject line “Mobile-first indexing enabled for www.yoursite.com.” If you haven’t received a notification, I would not assume that your site isn’t being moved to the mobile-first index. As is often the case with Search Console, the absence of information doesn’t tell you much.

Who is NOT affected by mobile-first indexing?

The Google Developer post about the mobile-first index (updated this week) very clearly outlines what kinds of sites will or will not be affected by this update.

This table from that post shows some of the most crucial information about the mobile-first indexing update.

Let’s break it down.

Your Site is Desktop Only

If your site is designed only for desktop users and does not change when a user is on a mobile device, mobile-first indexing will not affect you. That said, you should definitely tailor your site experience for mobile users if you care about SEO, since a growing majority of searches happen on mobile devices (and the data in this post is from 2016)!

Your Site is Responsive

A site using responsive design based on the viewport will not be affected by mobile-first indexing. This is because the “mobile version” of the site has the same content and code as the desktop version, so the indexed content will not change.

Your Site Exists Entirely in AMP

Good for you! If the only version of your site is built in AMP, your site is essentially already in the “mobile-first index”, because your site is streamlined for mobile users.

Who IS affected by mobile-first indexing? Your Site has Separate URLs for Mobile and Desktop Content

If your mobile site exists on a separate subdomain (such as m.yoursite.com), or you serve up mobile URLs in place of desktop URLs (yoursite.com/examplepage/mobile), mobile-first indexing WILL affect you. Google will start to index the mobile pages preferentially over the desktop pages

Your Site Dynamically Serves Content based on User Device

Similar to the scenario above, if your site is changing the content that a page delivers based on the device a user is on, the mobile versions of your pages will be going into the mobile-first index. The main difference between this and the Separate URLs scenario above is that your mobile content is not on a different URL or subdomain.

A quick note on these two cases, which could really be a separate blog post: We SEO talking-heads at Portent generally advise against separate URLs/different content for mobile users. Google Best Practices require you to deliver the same content on both versions of your pages. If you fail to do this, you could get flagged and penalized for cloaking, which is bad-news-bears. If at all possible, go with responsive design.

Your Site has AMP Versions of non-AMP Pages

This stands out to me as the most interesting part. If your site has AMP and non-AMP pages, “Google prefers the mobile version of the non-AMP URL for indexing.” In other words, mobile-first indexing will ignore your AMP pages and index regular versions of pages in their mobile forms. If you rely on AMP for your mobile experience, check to make sure your non-AMP pages work well on mobile devices.

Other Takeaways on Mobile-First Indexing

Everything in this post is contingent on whether you believe what Google says to be “true.” There’s nothing in the rulebook (nor in their track record) that says Google has to be 100% forthcoming, so take it all with a grain (or shaker) of salt.

The Official Google Webmaster post reinforces what we already know, but it’s good to hear it again: making a site mobile-friendly will help it perform better in mobile search results. A critically important example: fast-loading content helps a site perform better for users, and will perform better in organic search than slow-loading content after the update in July 2018.

We said it above, but it bears repeating: inclusion in the mobile-first index does not inherently mean you will rank higher.

This is all very new and exciting stuff, and I’m looking forward to hearing your thoughts. Have any of your clients received the Search Console notification that they’re being included? Have you seen any changes in how your site shows up in Google search?

https://ift.tt/2uIOBxn

[famlawatty6000]

What you Need to Know about Google’s Mobile-First Indexing Rollout

What you Need to Know about Google’s Mobile-First Indexing Rollout

Anyone reading this has probably already heard the news: Google announced last week that they’re “migrating sites that follow the best practices for mobile-first indexing.” Anyone who keeps abreast of SEO news (or works with clients who do) has probably received an email since that announcement wondering nervously what this means for their site.

Worry not!! This update to Google’s indexing process is not likely to affect your site or your clients’ sites, especially if you’re already following best practices for mobile friendliness. Unless you serve noticeably different content to mobile users than you do to desktop users, the mobile-first index should not change your rankings.

What exactly did Google announce?

This is not the first time Google has talked about mobile-first indexing. In November 2016, they announced that they’d “begun experiments to make [their] index mobile-first.” Now, the mobile-first index is being rolled out “more broadly”, starting with “sites that follow the best practices.”

The mobile-first index is not a separate Google index. Rather, Google will be replacing desktop versions of pages in its index with their mobile counterparts.

If a site you work on has been chosen as one of the lucky ones, you should have received a notification in Google Search Console with the subject line “Mobile-first indexing enabled for www.yoursite.com.” If you haven’t received a notification, I would not assume that your site isn’t being moved to the mobile-first index. As is often the case with Search Console, the absence of information doesn’t tell you much.

Who is NOT affected by mobile-first indexing?

The Google Developer post about the mobile-first index (updated this week) very clearly outlines what kinds of sites will or will not be affected by this update.

This table from that post shows some of the most crucial information about the mobile-first indexing update.

Let’s break it down.

Your Site is Desktop Only

If your site is designed only for desktop users and does not change when a user is on a mobile device, mobile-first indexing will not affect you. That said, you should definitely tailor your site experience for mobile users if you care about SEO, since a growing majority of searches happen on mobile devices (and the data in this post is from 2016)!

Your Site is Responsive

A site using responsive design based on the viewport will not be affected by mobile-first indexing. This is because the “mobile version” of the site has the same content and code as the desktop version, so the indexed content will not change.

Your Site Exists Entirely in AMP

Good for you! If the only version of your site is built in AMP, your site is essentially already in the “mobile-first index”, because your site is streamlined for mobile users.

Who IS affected by mobile-first indexing? Your Site has Separate URLs for Mobile and Desktop Content

If your mobile site exists on a separate subdomain (such as m.yoursite.com), or you serve up mobile URLs in place of desktop URLs (yoursite.com/examplepage/mobile), mobile-first indexing WILL affect you. Google will start to index the mobile pages preferentially over the desktop pages

Your Site Dynamically Serves Content based on User Device

Similar to the scenario above, if your site is changing the content that a page delivers based on the device a user is on, the mobile versions of your pages will be going into the mobile-first index. The main difference between this and the Separate URLs scenario above is that your mobile content is not on a different URL or subdomain.

A quick note on these two cases, which could really be a separate blog post: We SEO talking-heads at Portent generally advise against separate URLs/different content for mobile users. Google Best Practices require you to deliver the same content on both versions of your pages. If you fail to do this, you could get flagged and penalized for cloaking, which is bad-news-bears. If at all possible, go with responsive design.

Your Site has AMP Versions of non-AMP Pages

This stands out to me as the most interesting part. If your site has AMP and non-AMP pages, “Google prefers the mobile version of the non-AMP URL for indexing.” In other words, mobile-first indexing will ignore your AMP pages and index regular versions of pages in their mobile forms. If you rely on AMP for your mobile experience, check to make sure your non-AMP pages work well on mobile devices.

Other Takeaways on Mobile-First Indexing

Everything in this post is contingent on whether you believe what Google says to be “true.” There’s nothing in the rulebook (nor in their track record) that says Google has to be 100% forthcoming, so take it all with a grain (or shaker) of salt.

The Official Google Webmaster post reinforces what we already know, but it’s good to hear it again: making a site mobile-friendly will help it perform better in mobile search results. A critically important example: fast-loading content helps a site perform better for users, and will perform better in organic search than slow-loading content after the update in July 2018.

We said it above, but it bears repeating: inclusion in the mobile-first index does not inherently mean you will rank higher.

This is all very new and exciting stuff, and I’m looking forward to hearing your thoughts. Have any of your clients received the Search Console notification that they’re being included? Have you seen any changes in how your site shows up in Google search?

https://ift.tt/2uIOBxn

[duiatty48170]

What you Need to Know about Google’s Mobile-First Indexing Rollout

What you Need to Know about Google’s Mobile-First Indexing Rollout

Anyone reading this has probably already heard the news: Google announced last week that they’re “migrating sites that follow the best practices for mobile-first indexing.” Anyone who keeps abreast of SEO news (or works with clients who do) has probably received an email since that announcement wondering nervously what this means for their site.

Worry not!! This update to Google’s indexing process is not likely to affect your site or your clients’ sites, especially if you’re already following best practices for mobile friendliness. Unless you serve noticeably different content to mobile users than you do to desktop users, the mobile-first index should not change your rankings.

What exactly did Google announce?

This is not the first time Google has talked about mobile-first indexing. In November 2016, they announced that they’d “begun experiments to make [their] index mobile-first.” Now, the mobile-first index is being rolled out “more broadly”, starting with “sites that follow the best practices.”

The mobile-first index is not a separate Google index. Rather, Google will be replacing desktop versions of pages in its index with their mobile counterparts.

If a site you work on has been chosen as one of the lucky ones, you should have received a notification in Google Search Console with the subject line “Mobile-first indexing enabled for www.yoursite.com.” If you haven’t received a notification, I would not assume that your site isn’t being moved to the mobile-first index. As is often the case with Search Console, the absence of information doesn’t tell you much.

Who is NOT affected by mobile-first indexing?

The Google Developer post about the mobile-first index (updated this week) very clearly outlines what kinds of sites will or will not be affected by this update.

This table from that post shows some of the most crucial information about the mobile-first indexing update.

Let’s break it down.

Your Site is Desktop Only

If your site is designed only for desktop users and does not change when a user is on a mobile device, mobile-first indexing will not affect you. That said, you should definitely tailor your site experience for mobile users if you care about SEO, since a growing majority of searches happen on mobile devices (and the data in this post is from 2016)!

Your Site is Responsive

A site using responsive design based on the viewport will not be affected by mobile-first indexing. This is because the “mobile version” of the site has the same content and code as the desktop version, so the indexed content will not change.

Your Site Exists Entirely in AMP

Good for you! If the only version of your site is built in AMP, your site is essentially already in the “mobile-first index”, because your site is streamlined for mobile users.

Who IS affected by mobile-first indexing? Your Site has Separate URLs for Mobile and Desktop Content

If your mobile site exists on a separate subdomain (such as m.yoursite.com), or you serve up mobile URLs in place of desktop URLs (yoursite.com/examplepage/mobile), mobile-first indexing WILL affect you. Google will start to index the mobile pages preferentially over the desktop pages

Your Site Dynamically Serves Content based on User Device

Similar to the scenario above, if your site is changing the content that a page delivers based on the device a user is on, the mobile versions of your pages will be going into the mobile-first index. The main difference between this and the Separate URLs scenario above is that your mobile content is not on a different URL or subdomain.

A quick note on these two cases, which could really be a separate blog post: We SEO talking-heads at Portent generally advise against separate URLs/different content for mobile users. Google Best Practices require you to deliver the same content on both versions of your pages. If you fail to do this, you could get flagged and penalized for cloaking, which is bad-news-bears. If at all possible, go with responsive design.

Your Site has AMP Versions of non-AMP Pages

This stands out to me as the most interesting part. If your site has AMP and non-AMP pages, “Google prefers the mobile version of the non-AMP URL for indexing.” In other words, mobile-first indexing will ignore your AMP pages and index regular versions of pages in their mobile forms. If you rely on AMP for your mobile experience, check to make sure your non-AMP pages work well on mobile devices.

Other Takeaways on Mobile-First Indexing

Everything in this post is contingent on whether you believe what Google says to be “true.” There’s nothing in the rulebook (nor in their track record) that says Google has to be 100% forthcoming, so take it all with a grain (or shaker) of salt.

The Official Google Webmaster post reinforces what we already know, but it’s good to hear it again: making a site mobile-friendly will help it perform better in mobile search results. A critically important example: fast-loading content helps a site perform better for users, and will perform better in organic search than slow-loading content after the update in July 2018.

We said it above, but it bears repeating: inclusion in the mobile-first index does not inherently mean you will rank higher.

This is all very new and exciting stuff, and I’m looking forward to hearing your thoughts. Have any of your clients received the Search Console notification that they’re being included? Have you seen any changes in how your site shows up in Google search?

https://ift.tt/2uIOBxn

[duilawyer72210]

What you Need to Know about Google’s Mobile-First Indexing Rollout

What you Need to Know about Google’s Mobile-First Indexing Rollout

Anyone reading this has probably already heard the news: Google announced last week that they’re “migrating sites that follow the best practices for mobile-first indexing.” Anyone who keeps abreast of SEO news (or works with clients who do) has probably received an email since that announcement wondering nervously what this means for their site.

Worry not!! This update to Google’s indexing process is not likely to affect your site or your clients’ sites, especially if you’re already following best practices for mobile friendliness. Unless you serve noticeably different content to mobile users than you do to desktop users, the mobile-first index should not change your rankings.

What exactly did Google announce?

This is not the first time Google has talked about mobile-first indexing. In November 2016, they announced that they’d “begun experiments to make [their] index mobile-first.” Now, the mobile-first index is being rolled out “more broadly”, starting with “sites that follow the best practices.”

The mobile-first index is not a separate Google index. Rather, Google will be replacing desktop versions of pages in its index with their mobile counterparts.

If a site you work on has been chosen as one of the lucky ones, you should have received a notification in Google Search Console with the subject line “Mobile-first indexing enabled for www.yoursite.com.” If you haven’t received a notification, I would not assume that your site isn’t being moved to the mobile-first index. As is often the case with Search Console, the absence of information doesn’t tell you much.

Who is NOT affected by mobile-first indexing?

The Google Developer post about the mobile-first index (updated this week) very clearly outlines what kinds of sites will or will not be affected by this update.

This table from that post shows some of the most crucial information about the mobile-first indexing update.

Let’s break it down.

Your Site is Desktop Only

If your site is designed only for desktop users and does not change when a user is on a mobile device, mobile-first indexing will not affect you. That said, you should definitely tailor your site experience for mobile users if you care about SEO, since a growing majority of searches happen on mobile devices (and the data in this post is from 2016)!

Your Site is Responsive

A site using responsive design based on the viewport will not be affected by mobile-first indexing. This is because the “mobile version” of the site has the same content and code as the desktop version, so the indexed content will not change.

Your Site Exists Entirely in AMP

Good for you! If the only version of your site is built in AMP, your site is essentially already in the “mobile-first index”, because your site is streamlined for mobile users.

Who IS affected by mobile-first indexing? Your Site has Separate URLs for Mobile and Desktop Content

If your mobile site exists on a separate subdomain (such as m.yoursite.com), or you serve up mobile URLs in place of desktop URLs (yoursite.com/examplepage/mobile), mobile-first indexing WILL affect you. Google will start to index the mobile pages preferentially over the desktop pages

Your Site Dynamically Serves Content based on User Device

Similar to the scenario above, if your site is changing the content that a page delivers based on the device a user is on, the mobile versions of your pages will be going into the mobile-first index. The main difference between this and the Separate URLs scenario above is that your mobile content is not on a different URL or subdomain.

A quick note on these two cases, which could really be a separate blog post: We SEO talking-heads at Portent generally advise against separate URLs/different content for mobile users. Google Best Practices require you to deliver the same content on both versions of your pages. If you fail to do this, you could get flagged and penalized for cloaking, which is bad-news-bears. If at all possible, go with responsive design.

Your Site has AMP Versions of non-AMP Pages

This stands out to me as the most interesting part. If your site has AMP and non-AMP pages, “Google prefers the mobile version of the non-AMP URL for indexing.” In other words, mobile-first indexing will ignore your AMP pages and index regular versions of pages in their mobile forms. If you rely on AMP for your mobile experience, check to make sure your non-AMP pages work well on mobile devices.

Other Takeaways on Mobile-First Indexing

Everything in this post is contingent on whether you believe what Google says to be “true.” There’s nothing in the rulebook (nor in their track record) that says Google has to be 100% forthcoming, so take it all with a grain (or shaker) of salt.

The Official Google Webmaster post reinforces what we already know, but it’s good to hear it again: making a site mobile-friendly will help it perform better in mobile search results. A critically important example: fast-loading content helps a site perform better for users, and will perform better in organic search than slow-loading content after the update in July 2018.

We said it above, but it bears repeating: inclusion in the mobile-first index does not inherently mean you will rank higher.

This is all very new and exciting stuff, and I’m looking forward to hearing your thoughts. Have any of your clients received the Search Console notification that they’re being included? Have you seen any changes in how your site shows up in Google search?

https://ift.tt/2uIOBxn

[bathrem22032]

What you Need to Know about Google’s Mobile-First Indexing Rollout

What you Need to Know about Google’s Mobile-First Indexing Rollout

Anyone reading this has probably already heard the news: Google announced last week that they’re “migrating sites that follow the best practices for mobile-first indexing.” Anyone who keeps abreast of SEO news (or works with clients who do) has probably received an email since that announcement wondering nervously what this means for their site.

Worry not!! This update to Google’s indexing process is not likely to affect your site or your clients’ sites, especially if you’re already following best practices for mobile friendliness. Unless you serve noticeably different content to mobile users than you do to desktop users, the mobile-first index should not change your rankings.

What exactly did Google announce?

This is not the first time Google has talked about mobile-first indexing. In November 2016, they announced that they’d “begun experiments to make [their] index mobile-first.” Now, the mobile-first index is being rolled out “more broadly”, starting with “sites that follow the best practices.”

The mobile-first index is not a separate Google index. Rather, Google will be replacing desktop versions of pages in its index with their mobile counterparts.

If a site you work on has been chosen as one of the lucky ones, you should have received a notification in Google Search Console with the subject line “Mobile-first indexing enabled for www.yoursite.com.” If you haven’t received a notification, I would not assume that your site isn’t being moved to the mobile-first index. As is often the case with Search Console, the absence of information doesn’t tell you much.

Who is NOT affected by mobile-first indexing?

The Google Developer post about the mobile-first index (updated this week) very clearly outlines what kinds of sites will or will not be affected by this update.

This table from that post shows some of the most crucial information about the mobile-first indexing update.

Let’s break it down.

Your Site is Desktop Only

If your site is designed only for desktop users and does not change when a user is on a mobile device, mobile-first indexing will not affect you. That said, you should definitely tailor your site experience for mobile users if you care about SEO, since a growing majority of searches happen on mobile devices (and the data in this post is from 2016)!

Your Site is Responsive

A site using responsive design based on the viewport will not be affected by mobile-first indexing. This is because the “mobile version” of the site has the same content and code as the desktop version, so the indexed content will not change.

Your Site Exists Entirely in AMP

Good for you! If the only version of your site is built in AMP, your site is essentially already in the “mobile-first index”, because your site is streamlined for mobile users.

Who IS affected by mobile-first indexing? Your Site has Separate URLs for Mobile and Desktop Content

If your mobile site exists on a separate subdomain (such as m.yoursite.com), or you serve up mobile URLs in place of desktop URLs (yoursite.com/examplepage/mobile), mobile-first indexing WILL affect you. Google will start to index the mobile pages preferentially over the desktop pages

Your Site Dynamically Serves Content based on User Device

Similar to the scenario above, if your site is changing the content that a page delivers based on the device a user is on, the mobile versions of your pages will be going into the mobile-first index. The main difference between this and the Separate URLs scenario above is that your mobile content is not on a different URL or subdomain.

A quick note on these two cases, which could really be a separate blog post: We SEO talking-heads at Portent generally advise against separate URLs/different content for mobile users. Google Best Practices require you to deliver the same content on both versions of your pages. If you fail to do this, you could get flagged and penalized for cloaking, which is bad-news-bears. If at all possible, go with responsive design.

Your Site has AMP Versions of non-AMP Pages

This stands out to me as the most interesting part. If your site has AMP and non-AMP pages, “Google prefers the mobile version of the non-AMP URL for indexing.” In other words, mobile-first indexing will ignore your AMP pages and index regular versions of pages in their mobile forms. If you rely on AMP for your mobile experience, check to make sure your non-AMP pages work well on mobile devices.

Other Takeaways on Mobile-First Indexing

Everything in this post is contingent on whether you believe what Google says to be “true.” There’s nothing in the rulebook (nor in their track record) that says Google has to be 100% forthcoming, so take it all with a grain (or shaker) of salt.

The Official Google Webmaster post reinforces what we already know, but it’s good to hear it again: making a site mobile-friendly will help it perform better in mobile search results. A critically important example: fast-loading content helps a site perform better for users, and will perform better in organic search than slow-loading content after the update in July 2018.

We said it above, but it bears repeating: inclusion in the mobile-first index does not inherently mean you will rank higher.

This is all very new and exciting stuff, and I’m looking forward to hearing your thoughts. Have any of your clients received the Search Console notification that they’re being included? Have you seen any changes in how your site shows up in Google search?

https://ift.tt/2uIOBxn

[repumktg61602]

What you Need to Know about Google’s Mobile-First Indexing Rollout

What you Need to Know about Google’s Mobile-First Indexing Rollout

Anyone reading this has probably already heard the news: Google announced last week that they’re “migrating sites that follow the best practices for mobile-first indexing.” Anyone who keeps abreast of SEO news (or works with clients who do) has probably received an email since that announcement wondering nervously what this means for their site.

Worry not!! This update to Google’s indexing process is not likely to affect your site or your clients’ sites, especially if you’re already following best practices for mobile friendliness. Unless you serve noticeably different content to mobile users than you do to desktop users, the mobile-first index should not change your rankings.

What exactly did Google announce?

This is not the first time Google has talked about mobile-first indexing. In November 2016, they announced that they’d “begun experiments to make [their] index mobile-first.” Now, the mobile-first index is being rolled out “more broadly”, starting with “sites that follow the best practices.”

The mobile-first index is not a separate Google index. Rather, Google will be replacing desktop versions of pages in its index with their mobile counterparts.

If a site you work on has been chosen as one of the lucky ones, you should have received a notification in Google Search Console with the subject line “Mobile-first indexing enabled for www.yoursite.com.” If you haven’t received a notification, I would not assume that your site isn’t being moved to the mobile-first index. As is often the case with Search Console, the absence of information doesn’t tell you much.

Who is NOT affected by mobile-first indexing?

The Google Developer post about the mobile-first index (updated this week) very clearly outlines what kinds of sites will or will not be affected by this update.

This table from that post shows some of the most crucial information about the mobile-first indexing update.

Let’s break it down.

Your Site is Desktop Only

If your site is designed only for desktop users and does not change when a user is on a mobile device, mobile-first indexing will not affect you. That said, you should definitely tailor your site experience for mobile users if you care about SEO, since a growing majority of searches happen on mobile devices (and the data in this post is from 2016)!

Your Site is Responsive

A site using responsive design based on the viewport will not be affected by mobile-first indexing. This is because the “mobile version” of the site has the same content and code as the desktop version, so the indexed content will not change.

Your Site Exists Entirely in AMP

Good for you! If the only version of your site is built in AMP, your site is essentially already in the “mobile-first index”, because your site is streamlined for mobile users.

Who IS affected by mobile-first indexing? Your Site has Separate URLs for Mobile and Desktop Content

If your mobile site exists on a separate subdomain (such as m.yoursite.com), or you serve up mobile URLs in place of desktop URLs (yoursite.com/examplepage/mobile), mobile-first indexing WILL affect you. Google will start to index the mobile pages preferentially over the desktop pages

Your Site Dynamically Serves Content based on User Device

Similar to the scenario above, if your site is changing the content that a page delivers based on the device a user is on, the mobile versions of your pages will be going into the mobile-first index. The main difference between this and the Separate URLs scenario above is that your mobile content is not on a different URL or subdomain.

A quick note on these two cases, which could really be a separate blog post: We SEO talking-heads at Portent generally advise against separate URLs/different content for mobile users. Google Best Practices require you to deliver the same content on both versions of your pages. If you fail to do this, you could get flagged and penalized for cloaking, which is bad-news-bears. If at all possible, go with responsive design.

Your Site has AMP Versions of non-AMP Pages

This stands out to me as the most interesting part. If your site has AMP and non-AMP pages, “Google prefers the mobile version of the non-AMP URL for indexing.” In other words, mobile-first indexing will ignore your AMP pages and index regular versions of pages in their mobile forms. If you rely on AMP for your mobile experience, check to make sure your non-AMP pages work well on mobile devices.

Other Takeaways on Mobile-First Indexing

Everything in this post is contingent on whether you believe what Google says to be “true.” There’s nothing in the rulebook (nor in their track record) that says Google has to be 100% forthcoming, so take it all with a grain (or shaker) of salt.

The Official Google Webmaster post reinforces what we already know, but it’s good to hear it again: making a site mobile-friendly will help it perform better in mobile search results. A critically important example: fast-loading content helps a site perform better for users, and will perform better in organic search than slow-loading content after the update in July 2018.

We said it above, but it bears repeating: inclusion in the mobile-first index does not inherently mean you will rank higher.

This is all very new and exciting stuff, and I’m looking forward to hearing your thoughts. Have any of your clients received the Search Console notification that they’re being included? Have you seen any changes in how your site shows up in Google search?

https://ift.tt/2uIOBxn

[seo19107]

What you Need to Know about Google’s Mobile-First Indexing Rollout

What you Need to Know about Google’s Mobile-First Indexing Rollout

Anyone reading this has probably already heard the news: Google announced last week that they’re “migrating sites that follow the best practices for mobile-first indexing.” Anyone who keeps abreast of SEO news (or works with clients who do) has probably received an email since that announcement wondering nervously what this means for their site.

Worry not!! This update to Google’s indexing process is not likely to affect your site or your clients’ sites, especially if you’re already following best practices for mobile friendliness. Unless you serve noticeably different content to mobile users than you do to desktop users, the mobile-first index should not change your rankings.

What exactly did Google announce?

This is not the first time Google has talked about mobile-first indexing. In November 2016, they announced that they’d “begun experiments to make [their] index mobile-first.” Now, the mobile-first index is being rolled out “more broadly”, starting with “sites that follow the best practices.”

The mobile-first index is not a separate Google index. Rather, Google will be replacing desktop versions of pages in its index with their mobile counterparts.

If a site you work on has been chosen as one of the lucky ones, you should have received a notification in Google Search Console with the subject line “Mobile-first indexing enabled for www.yoursite.com.” If you haven’t received a notification, I would not assume that your site isn’t being moved to the mobile-first index. As is often the case with Search Console, the absence of information doesn’t tell you much.

Who is NOT affected by mobile-first indexing?

The Google Developer post about the mobile-first index (updated this week) very clearly outlines what kinds of sites will or will not be affected by this update.

This table from that post shows some of the most crucial information about the mobile-first indexing update.

Let’s break it down.

Your Site is Desktop Only

If your site is designed only for desktop users and does not change when a user is on a mobile device, mobile-first indexing will not affect you. That said, you should definitely tailor your site experience for mobile users if you care about SEO, since a growing majority of searches happen on mobile devices (and the data in this post is from 2016)!

Your Site is Responsive

A site using responsive design based on the viewport will not be affected by mobile-first indexing. This is because the “mobile version” of the site has the same content and code as the desktop version, so the indexed content will not change.

Your Site Exists Entirely in AMP

Good for you! If the only version of your site is built in AMP, your site is essentially already in the “mobile-first index”, because your site is streamlined for mobile users.

Who IS affected by mobile-first indexing? Your Site has Separate URLs for Mobile and Desktop Content

If your mobile site exists on a separate subdomain (such as m.yoursite.com), or you serve up mobile URLs in place of desktop URLs (yoursite.com/examplepage/mobile), mobile-first indexing WILL affect you. Google will start to index the mobile pages preferentially over the desktop pages

Your Site Dynamically Serves Content based on User Device

Similar to the scenario above, if your site is changing the content that a page delivers based on the device a user is on, the mobile versions of your pages will be going into the mobile-first index. The main difference between this and the Separate URLs scenario above is that your mobile content is not on a different URL or subdomain.

A quick note on these two cases, which could really be a separate blog post: We SEO talking-heads at Portent generally advise against separate URLs/different content for mobile users. Google Best Practices require you to deliver the same content on both versions of your pages. If you fail to do this, you could get flagged and penalized for cloaking, which is bad-news-bears. If at all possible, go with responsive design.

Your Site has AMP Versions of non-AMP Pages

This stands out to me as the most interesting part. If your site has AMP and non-AMP pages, “Google prefers the mobile version of the non-AMP URL for indexing.” In other words, mobile-first indexing will ignore your AMP pages and index regular versions of pages in their mobile forms. If you rely on AMP for your mobile experience, check to make sure your non-AMP pages work well on mobile devices.

Other Takeaways on Mobile-First Indexing

Everything in this post is contingent on whether you believe what Google says to be “true.” There’s nothing in the rulebook (nor in their track record) that says Google has to be 100% forthcoming, so take it all with a grain (or shaker) of salt.

The Official Google Webmaster post reinforces what we already know, but it’s good to hear it again: making a site mobile-friendly will help it perform better in mobile search results. A critically important example: fast-loading content helps a site perform better for users, and will perform better in organic search than slow-loading content after the update in July 2018.

We said it above, but it bears repeating: inclusion in the mobile-first index does not inherently mean you will rank higher.

This is all very new and exciting stuff, and I’m looking forward to hearing your thoughts. Have any of your clients received the Search Console notification that they’re being included? Have you seen any changes in how your site shows up in Google search?

https://ift.tt/2uIOBxn

[vidmrkting75038]

What you Need to Know about Google’s Mobile-First Indexing Rollout

What you Need to Know about Google’s Mobile-First Indexing Rollout

Anyone reading this has probably already heard the news: Google announced last week that they’re “migrating sites that follow the best practices for mobile-first indexing.” Anyone who keeps abreast of SEO news (or works with clients who do) has probably received an email since that announcement wondering nervously what this means for their site.

Worry not!! This update to Google’s indexing process is not likely to affect your site or your clients’ sites, especially if you’re already following best practices for mobile friendliness. Unless you serve noticeably different content to mobile users than you do to desktop users, the mobile-first index should not change your rankings.

What exactly did Google announce?

This is not the first time Google has talked about mobile-first indexing. In November 2016, they announced that they’d “begun experiments to make [their] index mobile-first.” Now, the mobile-first index is being rolled out “more broadly”, starting with “sites that follow the best practices.”

The mobile-first index is not a separate Google index. Rather, Google will be replacing desktop versions of pages in its index with their mobile counterparts.

If a site you work on has been chosen as one of the lucky ones, you should have received a notification in Google Search Console with the subject line “Mobile-first indexing enabled for www.yoursite.com.” If you haven’t received a notification, I would not assume that your site isn’t being moved to the mobile-first index. As is often the case with Search Console, the absence of information doesn’t tell you much.

Who is NOT affected by mobile-first indexing?

The Google Developer post about the mobile-first index (updated this week) very clearly outlines what kinds of sites will or will not be affected by this update.

This table from that post shows some of the most crucial information about the mobile-first indexing update.

Let’s break it down.

Your Site is Desktop Only

If your site is designed only for desktop users and does not change when a user is on a mobile device, mobile-first indexing will not affect you. That said, you should definitely tailor your site experience for mobile users if you care about SEO, since a growing majority of searches happen on mobile devices (and the data in this post is from 2016)!

Your Site is Responsive

A site using responsive design based on the viewport will not be affected by mobile-first indexing. This is because the “mobile version” of the site has the same content and code as the desktop version, so the indexed content will not change.

Your Site Exists Entirely in AMP

Good for you! If the only version of your site is built in AMP, your site is essentially already in the “mobile-first index”, because your site is streamlined for mobile users.

Who IS affected by mobile-first indexing? Your Site has Separate URLs for Mobile and Desktop Content

If your mobile site exists on a separate subdomain (such as m.yoursite.com), or you serve up mobile URLs in place of desktop URLs (yoursite.com/examplepage/mobile), mobile-first indexing WILL affect you. Google will start to index the mobile pages preferentially over the desktop pages

Your Site Dynamically Serves Content based on User Device

Similar to the scenario above, if your site is changing the content that a page delivers based on the device a user is on, the mobile versions of your pages will be going into the mobile-first index. The main difference between this and the Separate URLs scenario above is that your mobile content is not on a different URL or subdomain.

A quick note on these two cases, which could really be a separate blog post: We SEO talking-heads at Portent generally advise against separate URLs/different content for mobile users. Google Best Practices require you to deliver the same content on both versions of your pages. If you fail to do this, you could get flagged and penalized for cloaking, which is bad-news-bears. If at all possible, go with responsive design.

Your Site has AMP Versions of non-AMP Pages

This stands out to me as the most interesting part. If your site has AMP and non-AMP pages, “Google prefers the mobile version of the non-AMP URL for indexing.” In other words, mobile-first indexing will ignore your AMP pages and index regular versions of pages in their mobile forms. If you rely on AMP for your mobile experience, check to make sure your non-AMP pages work well on mobile devices.

Other Takeaways on Mobile-First Indexing

Everything in this post is contingent on whether you believe what Google says to be “true.” There’s nothing in the rulebook (nor in their track record) that says Google has to be 100% forthcoming, so take it all with a grain (or shaker) of salt.

The Official Google Webmaster post reinforces what we already know, but it’s good to hear it again: making a site mobile-friendly will help it perform better in mobile search results. A critically important example: fast-loading content helps a site perform better for users, and will perform better in organic search than slow-loading content after the update in July 2018.

We said it above, but it bears repeating: inclusion in the mobile-first index does not inherently mean you will rank higher.

This is all very new and exciting stuff, and I’m looking forward to hearing your thoughts. Have any of your clients received the Search Console notification that they’re being included? Have you seen any changes in how your site shows up in Google search?

https://ift.tt/2uIOBxn

[restatebrk24219]

What you Need to Know about Google’s Mobile-First Indexing Rollout

What you Need to Know about Google’s Mobile-First Indexing Rollout

Anyone reading this has probably already heard the news: Google announced last week that they’re “migrating sites that follow the best practices for mobile-first indexing.” Anyone who keeps abreast of SEO news (or works with clients who do) has probably received an email since that announcement wondering nervously what this means for their site.

Worry not!! This update to Google’s indexing process is not likely to affect your site or your clients’ sites, especially if you’re already following best practices for mobile friendliness. Unless you serve noticeably different content to mobile users than you do to desktop users, the mobile-first index should not change your rankings.

What exactly did Google announce?

This is not the first time Google has talked about mobile-first indexing. In November 2016, they announced that they’d “begun experiments to make [their] index mobile-first.” Now, the mobile-first index is being rolled out “more broadly”, starting with “sites that follow the best practices.”

The mobile-first index is not a separate Google index. Rather, Google will be replacing desktop versions of pages in its index with their mobile counterparts.

If a site you work on has been chosen as one of the lucky ones, you should have received a notification in Google Search Console with the subject line “Mobile-first indexing enabled for www.yoursite.com.” If you haven’t received a notification, I would not assume that your site isn’t being moved to the mobile-first index. As is often the case with Search Console, the absence of information doesn’t tell you much.

Who is NOT affected by mobile-first indexing?

The Google Developer post about the mobile-first index (updated this week) very clearly outlines what kinds of sites will or will not be affected by this update.

This table from that post shows some of the most crucial information about the mobile-first indexing update.

Let’s break it down.

Your Site is Desktop Only

If your site is designed only for desktop users and does not change when a user is on a mobile device, mobile-first indexing will not affect you. That said, you should definitely tailor your site experience for mobile users if you care about SEO, since a growing majority of searches happen on mobile devices (and the data in this post is from 2016)!

Your Site is Responsive

A site using responsive design based on the viewport will not be affected by mobile-first indexing. This is because the “mobile version” of the site has the same content and code as the desktop version, so the indexed content will not change.

Your Site Exists Entirely in AMP

Good for you! If the only version of your site is built in AMP, your site is essentially already in the “mobile-first index”, because your site is streamlined for mobile users.

Who IS affected by mobile-first indexing? Your Site has Separate URLs for Mobile and Desktop Content

If your mobile site exists on a separate subdomain (such as m.yoursite.com), or you serve up mobile URLs in place of desktop URLs (yoursite.com/examplepage/mobile), mobile-first indexing WILL affect you. Google will start to index the mobile pages preferentially over the desktop pages

Your Site Dynamically Serves Content based on User Device

Similar to the scenario above, if your site is changing the content that a page delivers based on the device a user is on, the mobile versions of your pages will be going into the mobile-first index. The main difference between this and the Separate URLs scenario above is that your mobile content is not on a different URL or subdomain.

A quick note on these two cases, which could really be a separate blog post: We SEO talking-heads at Portent generally advise against separate URLs/different content for mobile users. Google Best Practices require you to deliver the same content on both versions of your pages. If you fail to do this, you could get flagged and penalized for cloaking, which is bad-news-bears. If at all possible, go with responsive design.

Your Site has AMP Versions of non-AMP Pages

This stands out to me as the most interesting part. If your site has AMP and non-AMP pages, “Google prefers the mobile version of the non-AMP URL for indexing.” In other words, mobile-first indexing will ignore your AMP pages and index regular versions of pages in their mobile forms. If you rely on AMP for your mobile experience, check to make sure your non-AMP pages work well on mobile devices.

Other Takeaways on Mobile-First Indexing

Everything in this post is contingent on whether you believe what Google says to be “true.” There’s nothing in the rulebook (nor in their track record) that says Google has to be 100% forthcoming, so take it all with a grain (or shaker) of salt.

The Official Google Webmaster post reinforces what we already know, but it’s good to hear it again: making a site mobile-friendly will help it perform better in mobile search results. A critically important example: fast-loading content helps a site perform better for users, and will perform better in organic search than slow-loading content after the update in July 2018.

We said it above, but it bears repeating: inclusion in the mobile-first index does not inherently mean you will rank higher.

This is all very new and exciting stuff, and I’m looking forward to hearing your thoughts. Have any of your clients received the Search Console notification that they’re being included? Have you seen any changes in how your site shows up in Google search?

https://ift.tt/2uIOBxn