Please don't remove m=1? from blog post URL with JavaScript
m=1? is not a problem actually. In the google search console, it is common problem that, coverage reports shows excluded.
There are six types of excluded problems in the google search console.
- Alternate page with proper canonical tag
- Not found (404)
- Crawled - currently not indexed
- Page with redirect
- Duplicate without user-selected canonical
- Discovered- currently not indexed.
We usually think excluded is a problem. But it is not a major problem. It is a common issue in every blog. The main problem is the Error(red) Problem. So you should be cool and calm and don't worry about the excluded problems.
Why you should not use javascript to remove m=1?
Because javascript remove m=1? only from the post URL not from the content page. Actually, javascript doesn't remove m=1? from the blog page it only suppressed m=1? from the URL. But the m=1? run on backend.
Why is coverage show excluded?
Because your same post has two URLs. One is for the PC version and another is the mobile version and the mobile version contains m=1?. As your blog post URL which does not contain m=1? is indexed successfully the mobile URL makes canonical with indexed URL.So don't worry about canonical URL because the main URL crawled and indexed successfully.
Important Note: You can get Google AdSense approval if you have lots of excluded posts. Because excluded is not a major problem. The major problem is the Error problem in the google search console.
0 Comments