As far as you can tell, you’ve done everything right. You wrote a new blog post. It’s lengthy, it’s authoritative, it’s well-written and proofread. You’ve included a bunch of links to authoritative sources. You’ve included compelling images. It’s all set for publication, with a catchy title and well-formulated meta data.
You hit that “publish” button and walk away, secure in the knowledge that you did a good job. This post should be a hit. And yet, when you check the next day, you can’t find the post. What’s going on?
The simplest possible issue, albeit a rare cause for this problem, is simply that your local cached version of your own website doesn’t have the new post. You visit your homepage, but your cache hasn’t expired, so your browser doesn’t check to see if the page has changed. Your new post is live, but you can’t see it.
The solution to this is as simple as the problem is rare. Simply force a refresh of the page that refreshes the cache. On some browsers this just means hitting F5, or hitting ctrl+F5 or shift+F5. Typically, though, this won’t be the problem; modern caches are good at checking for incremental changes.
One of the more common reasons why you might not be able to find your post is that you “published” it as a saved draft rather than a published, live piece. If you’re used to saving posts as drafts and publishing them later, or saving them as drafts with a publication date in the future, this could be your problem.
Go into your blog CMS and look for your post. What is the post status? It should be published or live, if you want the post to be visible. If the post status is something like “saved as draft” or “scheduled”, your post isn’t live and published.
I’ve had this issue once or twice when scheduling a post in the future, accidentally setting the month one too high, or even setting the year incorrectly. A post I thought was going to go up the next day actually was scheduled to go up 366 days from now.
Luckily, this is a very easy problem to solve. Simply change the publication date, or even click the “publish now” button instead of letting it publish on a schedule. Sure, it might throw off the carefully calculated timing you set up for your post publication, but it’s better to publish a post a few hours or a day late than to miss an editorial content slot entirely.
If your post is labeled as published, and you can view it on your own website, but it doesn’t show up in Google’s search, that’s when you might have more insidious issues. Let’s look at those next.
If you want to know why your site might not be visible in Google search, one of the first things you should learn is how Google finds new content. They actually have several different mechanisms in play looking for new content, either in the form of new blog posts on an existing website or in the form of a new website entirely.
Here are the various ways Google uses to find new content. Also, note that when I say “Google” I’m really just using it as shorthand for any search engine. Other search engines work in much the same way, though they may have less power, fewer avenues, and a slower indexation speed, depending.
Anything that makes it difficult or impossible for Google to find a piece of content is a roadblock that can prevent your articles from showing up in the Google search index. Here are some of the more common causes.
If your site is brand new, Google will be indexing it at a slower pace before they add it to their main search index. They do this for a few reasons. First, they want to prevent pages from being indexed as good and then being edited to be malicious. They monitor pages for a short time to see if they’re changing frequently. It doesn’t do anyone any good if Google indexes a page that then changes completely before it even has time to circulate.
If it has been more than a few days since your site should have been indexed, it’s possible that it simply hasn’t been given any attention. You can take steps using Google services to try to “force” your site to be indexed. Add your site as a new property in Google webmaster tools and Google analytics. Submit a sitemap to Google manually. These should be adequate to tell Google “hey, I have a page here for you to look at.”
A common technique for building a new website is to upload some of it online to test. However, since you don’t want Google indexing half-baked pages and issuing penalties before you’re even up and running, it’s not uncommon to block all robots from viewing your page until you’re ready for it to go live.
The problem here is if you haven’t removed these robot-blocking directives from your site before going live for real. If you’re still blocking robots, it doesn’t matter how many times you submit a sitemap, you’re telling Google to eff off.
There are two places where you can find robots directives. The first is a generalized robots.txt file in your root directory for your website. This file is a basic text file and tells robots what to do on your site. Typically, this is used to block indexing of system pages, like the admin login page, or landing pages you’re split testing and don’t want indexed.
Check to see if you have a robots.txt file, and if so, if there’s anything in it. Look for any of the Google user-agents and whether or not you’ve disallowed them. You can read more about that here.
The other place you can find robots directives is in the meta data of your pages themselves. A line of code that looks like “<meta name=”robots” content=”noindex, nofollow”>” will be blocking robots from your page. You’ll need to remove this line for your page to be visible. Again, more on this here.
If your content just isn’t indexed, you can look for other fringe issues that might be causing a problem.
These issues typically affect indexation more than ranking; if you are indexed but don’t rank, that’s another problem to discuss.
Another common problem is the misconception that indexation means that you’re going to show up in any preferential position in the Google search index. Just because you’re in the database doesn’t mean you’re going to float to the top, right?
To check to make sure your content is indexed, but isn’t ranking, do a site search. Go to Google and type in “site:yourdomain.com” followed by the title of the blog post you’re looking for. For example, the post you’re reading right now would be “site:blogpros.com Why Aren’t My Blog Posts Showing Up In Google?”
Look for your content in the search results. If it’s not there, you’ll see a search results page with your search “did not match any documents”. To make sure your site as a whole is indexed and it’s just that post that’s not there, do a blank site search for your domain and see what pops up. If it’s “nothing”, then your site isn’t indexed. If other pages show up, you just have a problem with one post.
Incidentally, this can show you if you have issues with pages being indexed when you don’t want them to be. If you see system pages you don’t want indexed, make sure to add a robots directive to those pages.
If your content is indexed properly and shows up in the site search, your issue is not with your indexation, but with your ranking. That’s an entirely different subject.
If your site isn’t ranking, even though it’s indexed and you believe the content is fine, you might be operating under a Google search penalty. These can be tricky to identify. The easiest way to identify them is to visit your Google search console and look to see if there are any manual actions in place.
Manual actions typically mean there’s some issue with your page. These can include issues with redirects and cloaked links, sites with hidden or cloaked text and keyword spam, pages with thin content, and so on. You can read a full list of penalties and the solutions to them here.
If, as it so often turns out, the issue is simply time, there’s not much you can do about it.
That said, you can take some steps to encourage indexation for your new content.
And so on. Making sure your content is indexed properly is step one of running a good website. It’s a fundamental you need to fully understand before you can focus on ranking properly.