How I Set Up My Website to Be Found on Google: A Practical Checklist

A website can be live, fast and well designed and still be almost invisible on Google. I learned this the practical way while setting up my own site, where Google was showing a page that no longer existed, and my images were not showing up at all.

This post is the checklist I worked through, in the order that made sense. It also includes the mistakes, because those are the parts that are easy to repeat. One thing up front: nobody can promise you a ranking, and I will not either. What you can do is remove the obstacles and give Google clear information.

Start by proving the site is yours

Google Search Console is a free tool that shows you how Google sees your site. To use it you first have to prove you own the site. There are a few ways to do that. I used a DNS record, which means adding one small text entry to the domain's settings. It does not touch the website's code, and it does not affect how the site ranks. It only tells Google that you control the domain.

Once the site is verified you get the useful parts: which pages are indexed, which ones have problems, and what people searched for before they found you.

Give Google a map of your site

A sitemap is a file that lists the pages you want found. Mine is generated automatically from the database, so a new article appears in it the moment I publish it, with no manual editing. I also list the sitemap's address in the site's robots file so that any search engine can find it without being told.

If images matter to you, as they do for a portfolio, add them to the sitemap too. Mine now lists the profile photo, the gallery and the cover image of every project and article, each with a short title. It does not guarantee that the images appear in image search, but it makes sure Google knows they exist.

Fix the old addresses that no longer exist

This was the surprise. A search that included my name showed a listing called profile, and the link led to a not found error. At some point an old page at that address had been indexed, and when it disappeared Google kept the listing.

The fix is a permanent redirect, which tells browsers and search engines that the old address now lives somewhere else. I pointed the old address at my About page. The next step is to ask Google to look at the old address again so it notices the change. If you have ever renamed or deleted pages, check Search Console for not found errors and redirect the ones that still matter.

Make every page explain itself

Search engines read what is on the page, so give them clear material. Each page should have its own title and a short description written for a person, not stuffed with keywords. Every meaningful image should have alt text that describes it, for example my name and what I do rather than the word image.

You can also add structured data, a small block of machine-readable information. On my home page it states who I am, my job and my social profiles. On articles it states the title, the publish date, the author and the publisher. On every article it also describes the path from the home page to the article, which is what lets search results show a tidy trail instead of a bare web address.

Show a real author and a real date

I found a gap in my own blog here. A post only showed a byline if someone had remembered to choose an author, and the field was blank by default. A post saved without one would have had no visible author. The author now defaults to whoever is logged in, and the page falls back to the site name if it is ever empty. Readers trust articles more when they can see who wrote them and when, and so do search engines that care about news-style content.

Offer a feed for new posts

An RSS feed is a simple file listing your newest articles. Feed readers and Google can both use it to learn about new posts quickly. I added one and submitted it in Search Console, and it was the first thing Google processed successfully.

I also added a news sitemap. It only lists articles from the last two days, which means it is empty when you have not published recently, and Search Console reported that as an error. That is worth knowing before you panic. Google News is a separate program with its own requirements and a review process, and a personal blog may not qualify for it, so I treat the news sitemap as a bonus and not a goal.

Test before you deploy

Here is my own mistake. When I added the image sitemap, I deployed it without opening it first. A typo in one line made the sitemap return a server error for a few minutes. Googlebot can arrive at any time, so a few minutes is enough to cause a failed fetch.

The fix for next time is simple. Open the file locally and make sure it loads, check that the content is valid, and confirm the live address returns a normal response afterwards. It takes a minute and would have avoided the problem.

Be patient and be honest about results

After submitting my sitemap, Search Console showed a Couldn't fetch status for a while, even though the server logs proved that Googlebot had received the file successfully. That status is often just a delay. If it persists after a day or so, remove the sitemap and submit it again.

Indexing takes days to weeks. Appearing for your own name is realistic for a personal site, but appearing high for competitive topics depends on the quality of what you write and on other sites linking to you. No setting replaces that.

The short version

Verify the site in Search Console. Publish a sitemap and reference it in your robots file. Redirect old addresses that no longer exist. Give every page a clear title, description and image alt text. Show real authors and dates. Offer a feed. Test every change before you deploy it, and then be patient.

If you would like help getting your own business website found, get in touch through the contact page.