I am facing an issue that Google Bot is reporting some unknown URLs (as highlighted in the screenshot) from one type of page. After checking the source code, JS and CSS files I have not come across any such URLs. Because of them the 404 count reported by Google Search Console is continuously increasing.
Can anyone please, guide me in finding the root cause as to why crawler is reporting such URLs or how to avoid them.
Most of the cases, these URLs are coming from outside backlinks to your website, check your backlinks from "Links to my site"
Or maybe your domain was on another website and your bought it.
Also check if you have spammy comments on your website.
Related
I recently took on a new client who had an existing web presence with their domain, and the old build structure of the links, Google is still indexing those sub-title links on the search result for the company as the old links. I have re-submitted the sitemap on Google Search console, tried re-indexing them individually, and also tried submitting removal requests for domains with certain suffixes. None of this has changed the links Google is bringing up in search, still the old links. The proper links are scattered in there, but not the top results.
I asked to the Google Search forum and we found that the pages are still returning a 200 status code, and not a true 404 status code when the page does not exist on the site (see below). My app is built with React.js and hosted with Firebase Hosting on Google Cloud Platform. I am not seeing a lot of information online on how to fix this issue I am having so my Error Boundary in React is sending a true 404 error. Or if client side status code sending is not possible, then doing so on the Firebase side. Any ideas out there on how to fix the primary issue of Google promoting dead links under main link for a website?
I deployed my page with firebase hosting.
For some reason, I get this safety error:
Users can write and read data from firebase (comments, replies), but can't of course read data for users collection. Did anyone have same problem? What can I do about it?
Here are links to:
live web site https://interactive-comment-sect-a2a31.web.app/
github repo https://github.com/tr43om/Texto
The issue could result with any of the following reason:
Your site has been infected with malware
Your site contains phishing pages
There's an issue with your SSL certificate
Your plugins have security vulnerabilities
Your website has questionable links
You offer suspicious downloads
To detect issue, use google search console and fix the issue as per recommendation.
source
Your Firebase API key is open to see anyone. It means your database can be hacked anytime. I think this can be an issue. Try to put your keys inside .env file. That will make your application more secure.
I have an AngularJS SPA site which I wanted to test using google's "Fetch as Google" feature in webmaster tools. I am a little confused about the results. The screenshot from Googlebot looks correct however the response doesn't include any of the contents inside the "ui-view" (ui-router)... can someone explain what is happening here? Is google indexing the site properly since the screenshot is correct? Or is google not able to execute the JS properly for indexing?
This is a mixed bag. From some tests I've seen the GoogleBot is able to index some of the AJAX fetched content in some cases. A safe bet though to make all the search engines happy is to use prerender.io or download their open source stuff (uses PhantomJS) to have your site be easily indexable. Basically what this does is saves the version of your site after async operations have completed for a given URL and then you setup a redirect on your server that points any of the potential bots for search engines over to the preprocessed page. It sounds pretty complicated but following the instructions on the site it's not too hard to setup, and if you don't want to pay for prerender.io to serve cached copies of your pages to search engines you can run the server component yourself too.
I am trying to register my web app for the service of Google AdSense.
After five attempts are still stuck in the first phase for the error: Content insufficient.
My web app is a search engine for youtube, developed with AngularJs and NodeJs
AngularJS fully embraces the asynchronous model and this is what creates problems for Google's crawlers. So I implemented the library prerender.io and I have set up the meta tag to fix any problems with the # of Angular.
<meta name = "fragment" content = "">
I also prepared the sitemap.xml within the site, and that index the pages through the portal of google for webmasters.
The site being a search engine, does not have static content and reach, so I also added some texts and descriptions in the page principle, which houses the other partial files.
Despite these changes, I could not pass the first stage, how can I do to fix?
I'm not making all the necessary steps for a web app Angular?
To be approved in Google Adsense you need about 10 topics of 400 words. The content should be unique. According to Google Adsense TOS it is not allowed to put ads in pages having copied content. So in your case if you provide search results you will provide copied content.
Short of paying $150/month so I can actually submit a ticket, what can I do to get Google's attention? I've seen other people get help for what appears to be the exact same issue.
I uploaded a new (small) app to Google App Engine (GAE), and the Applications Settings page shows an error under Cloud Integration ("An error occurred when creating the project. Please retry").
I've retried over a period of days, but it tries for a while, then reports another failure. I've asked questions of StackOverflow, and in the GAE issues forum, to no response.
Try to get hold of the people from Google Developer relations here, in the relevant Google+ communities or on Google groups.
If it can bring you any comfort: paying the $150 does not help you much - we have the subscription.
If you have a second Google Apps domain, replicate the issue by switching domains and recreating the project from scratch. Then if the error occurs again, post that it occurs in 2 or more cloud.google.com accounts with separate domains. This should help show this is not a one off error and requires investigation.
If it does not occur in the second domain, save your data, delete your project and recreate with a different project name and number.
-ExGenius