Google Analytics 4 and Search Console for Travel Blogs

Here’s the short version, because I know you want to get on with it. To set up Google Analytics 4 and Search Console for a travel blog, you create a free GA4 property with a web data stream at analytics.google.com, install its tag on your WordPress site (the Site Kit plugin does this in a few clicks), then add your domain to Search Console, verify it with a DNS record or HTML tag, and submit your Yoast sitemap. The whole thing takes about 45 minutes and costs nothing. Zero. After that you check three GA4 reports and one Search Console report once a week and get on with your life. This is the 2026 version: GA4 only, since Universal Analytics has been gone since 2023 and any tutorial waving a “UA-” code at you is out of date.

GA4 vs Search Console: what’s the difference and why do you need both?

Beginners mix these two up constantly, and fair enough, because they’re both free Google tools with dashboards full of graphs. But they measure opposite ends of the same journey.

Google Search Console is Google telling you, from its side of the fence, how your site is doing in search: which queries showed your pages, how often, how many people clicked, which pages are indexed, which have problems. It’s free, it’s first-party, and it’s the single most useful SEO tool a travel blogger will ever own. I mean that. No paid keyword tool can tell you which queries you’re already sitting on page two for… Search Console can, and it costs nothing.

Google Analytics 4 runs on your site and records what visitors do after they arrive, whether they came from Google, Pinterest, email, Instagram or anywhere else: which pages they read, how long they stick around, what they click, whether they came back. It’s how you answer “is Pinterest actually worth my time?” and it’s where the numbers for your media kit come from when a brand finally emails. So yes, you want it.

One more reason to do this NOW rather than “when I have traffic”: both tools only record from the day you connect them. Every client who’s come to me a year in and asked “what did my traffic look like at launch?” gets the same sad answer: nobody knows. Haven’t got a live site yet? Follow the seven-step guide to starting a travel blog first; this post assumes WordPress is installed and you can log in.

How to create a GA4 property and web data stream

You’ll need a Google account. A Gmail address is fine, but I’d create a fresh one for the blog rather than using your personal one; it makes handing things over later (to a VA, a buyer, a developer like me) so much easier. Then:

1. Go to analytics.google.com and sign in. First time? You’ll see a Start measuring button; otherwise click the Admin gear at the bottom left.
2. Account: name it after yourself or your blog. One account can hold several properties, so if you start a second blog later (people do), you add it here.
3. Property: click Create property (in the Property column if you’re in Admin). Name it your blog’s name, set your reporting time zone and currency. The time zone matters; leave it on US Pacific and your “days” will be wrong forever.
4. Answer the business details questions (industry: Travel, size: small). Pick any objective; it only affects which reports are pre-selected, and you can change it later.
5. Data stream: choose Web. Enter your site URL with https and no trailing slash, and a stream name (just your domain). Leave Enhanced measurement switched on; it automatically tracks scrolls, outbound clicks, site search and file downloads, which is most of what a blogger wants anyway.
6. Click Create and continue (the exact wording is “Create stream” on some accounts). You’ll land on the stream details page showing your Measurement ID, which looks like G-XXXXXXXXXX. Copy it.

Two settings worth changing straight away while you’re in Admin. Under Data collection and modification → Data retention, change event data retention from the default 2 months to 14 months, so next year you can compare this year with last year. And under Data streams → your stream → Configure tag settings → Show all → List unwanted referrals, add your own domain so your own pages don’t show up as a “referral” source. Two minutes, and you’ll thank yourself later.

How to install GA4 on WordPress: Site Kit vs theme header

You’ve got your Measurement ID. Now the tag has to load on every page of your site. There are three sensible ways to do it, and one that I see far too often on sites I inherit and would steer you well away from.

Method	Difficulty	Also connects Search Console?	Best for	Watch out for
Site Kit by Google plugin	Easy: sign in, click through	Yes, in the same wizard	Almost every beginner	Adds a dashboard widget and a small script; fine on a lean site
Theme’s “header scripts” field or a code-snippets plugin	Easy: paste the snippet	No, verify Search Console separately	People who want the minimum number of plugins	Snippet is lost if you switch theme; make a note of where you put it
Google Tag Manager	Moderate	No	Bloggers who’ll add affiliate click tracking, ads pixels, etc. later	Overkill on day one; another dashboard to learn
Editing header.php in the parent theme	Looks easy	No	Nobody	Wiped on the next theme update; you’ll lose weeks of data without noticing

Option A: install GA4 (and Search Console) with Site Kit

Site Kit by Google is Google’s own free WordPress plugin. It handles the tag, the Search Console verification and a summary dashboard in one go. Here’s the flow as of 2026:

1. In WordPress go to Plugins → Add New Plugin, search “Site Kit by Google”, click Install Now, then Activate.
2. Click Start setup on the banner (or Site Kit → Dashboard). Tick the box to connect Google Analytics as part of setup if it’s offered, then Sign in with Google using the account you created the GA4 property with.
3. Grant the permissions it asks for. Site Kit will verify site ownership (it places a verification token for you), ask to allow Google to access data, and set up Search Console: if the site isn’t already a Search Console property, it adds it.
4. For Analytics, choose your existing account, property and web data stream from the dropdowns. (Skipped the previous section? Site Kit can create a property for you right here instead.) Leave “Place Google tag on your site” enabled and click Configure Analytics or Complete setup.
5. Open your homepage in a private browser window, then check Reports → Realtime in GA4. You should see yourself as one active user within a minute or so. If you do, it’s working. Brilliant.

Site Kit’s own dashboard is fine for a quick glance but limited; you’ll still open GA4 and Search Console directly for the reports that actually matter. One heads-up: Site Kit and Search Console data can take a day or two to start showing up. Realtime in GA4 is the only place you’ll see anything straight away, so don’t panic at an empty dashboard on day one.

Option B: add the GA4 snippet to your theme header

Rather not add a plugin? Fair enough. GA4 gives you a snippet to paste. In GA4, go to Admin → Data streams → your web stream, scroll to Google tag and click View tag instructions, then the Install manually tab. Copy the whole block; it starts with <!-- Google tag (gtag.js) --> and contains your G- ID twice.

Where you paste it depends on your theme. Loads of travel themes have a “Header scripts” or “Custom code” box under Appearance → Customize or in the theme’s options panel. If yours doesn’t, install a small code-snippets plugin such as WPCode (formerly Insert Headers and Footers) and paste it into the header section there. Both routes survive theme updates. Editing header.php directly does not, unless you’re on a child theme, and even then it’s the wrong place for it. I’m a developer and I still wouldn’t do it.

Whichever route you take, install it ONCE. Site Kit plus a manual snippet means every visit counts twice and your numbers are useless. Not sure? View your homepage source (right-click → View page source) and search for “gtag”; you should find your G- ID exactly once.

A word on cookie consent

If you expect readers in the EU or UK (and every travel blog does), you need a cookie consent banner that blocks analytics until the visitor agrees, plus a privacy policy that mentions Google Analytics. This isn’t optional decoration; it’s the law in those places. The legal pages every travel blog needs post covers the banner plugins and the policy wording, and Site Kit supports Google’s consent mode when a compatible consent plugin is installed. Boring, but do it.

The GA4 reports a travel blogger should actually check

GA4 has dozens of reports and an “Explore” section that can build almost anything. You need about three. Three! Everything below lives under Reports in the left-hand menu of GA4; the exact grouping can shift a bit depending on the business objective you chose, so if a report isn’t where I say it is, don’t panic, just use the search box at the top of GA4.

Report	Where	What to look at	Question it answers
Reports snapshot	Reports → Reports snapshot	Users, new users, the trend line	Is traffic going up or down this month?
Traffic acquisition	Reports → Acquisition → Traffic acquisition	Session default channel group: Organic Search, Organic Social, Direct, Referral, Email	Where do my visitors come from? Is Pinterest or Google working?
Pages and screens	Reports → Engagement → Pages and screens	Views and average engagement time per page path	Which posts do people read? Which should I update or link to more?
Engagement overview	Reports → Engagement → Overview	Average engagement time, engaged sessions per user	Are people actually reading, or bouncing?
Realtime	Reports → Realtime	Users in the last 30 minutes	Is the tag working? Did that Pinterest pin just take off?
Demographics (Country)	Reports → User → User attributes → Demographic details	Users by country	Who’s reading, for the media kit and for deciding currencies and dates

Traffic acquisition: where visitors come from

This is the one I’d open first every week. It groups sessions by channel, and for a new travel blog the rows you care about are Organic Search (Google, Bing), Organic Social (Pinterest, Instagram, Facebook), Direct (people typing your URL, bookmarks, and anything GA4 couldn’t pin down) and Referral (links from other sites). Change the primary dimension dropdown from “Session default channel group” to Session source / medium to see individual sources like pinterest / referral or google / organic. Set the date range at the top right to the last 28 days and compare with the previous period; a small blog’s daily numbers are far too noisy to mean anything, trust me.

Pages and screens: what they read

Sort by Views to see your most-read posts. Then look at Average engagement time for each one: a 2,000-word itinerary with 20 seconds of engagement is being clicked and abandoned, which usually means the top of the post isn’t answering the question the searcher actually had. That’s a rewrite candidate. A post with high engagement but few views is a link candidate: stick it in your menu, link to it from other posts, pin it. This report is also where you’ll discover your About page is getting way more visits than you expected… which is exactly why it’s worth writing a proper About page early.

Engagement overview: are they reading?

GA4 replaced the old “bounce rate” thinking with engaged sessions: a session that lasted more than 10 seconds, had a conversion event, or included two or more page views. Average engagement time per session is the number to watch over months, not days. For a text-heavy travel blog, watching it climb as you sharpen your writing and internal linking is a far better signal than raw visitor counts, which will be small for a while. That’s normal, by the way. The guide to growing a travel blog audience from zero shows what a realistic first-year traffic curve actually looks like.

How to set up Google Search Console for your travel blog

If you used Site Kit, Search Console is probably already connected and you can jump to the sitemap step, but read the property-type note below anyway. If you installed GA4 manually, or you want the sturdier setup that survives everything, do this:

1. Go to search.google.com/search-console and sign in with the same Google account.
2. Click Add property. You get two choices: Domain or URL prefix.
3. Choose one and verify (details below).
4. Submit your sitemap under Sitemaps in the left menu.

Domain property (DNS) vs URL-prefix property (HTML tag)

Here’s the difference in plain words. A Domain property (you type yourblog.com) covers every version of your site at once: http and https, www and non-www, and any subdomains. It can only be verified with a DNS TXT record. A URL-prefix property (you type https://yourblog.com/) covers only that exact prefix, but it gives you more ways to verify: an HTML tag in your site’s head, an HTML file upload, or your existing Google Analytics or Tag Manager tag. Google’s verification help page lists the lot if you’re curious.

My pick, every time: the Domain property. It’s a one-off DNS record that survives theme changes, plugin removals and host migrations, and you never end up with the classic mess of four separate properties for the four versions of your URL (I’ve cleaned that up more times than I’d like). Here’s the DNS route:

1. Select Domain, enter your bare domain, click Continue. Search Console shows a TXT record value beginning google-site-verification=. Copy it.
2. Log in wherever your DNS lives. If you bought the domain with your hosting (as you would on Bluehost following the install WordPress on Bluehost walkthrough), that’s the hosting dashboard’s Domains → DNS section. If you use Cloudflare, it’s the DNS tab there.
3. Add a record: type TXT, name/host @ (or leave blank, or your bare domain, depending on the provider), value: paste the verification string. Save.
4. Back in Search Console, click Verify. DNS changes can take anywhere from a minute to a day to propagate; if it fails, make a cup of tea, wait an hour and try again rather than adding the record twice.

If DNS is a step too far right now, no shame in it: the URL-prefix route with the HTML tag is fine. Choose URL prefix, enter your full https URL, pick HTML tag, and paste the <meta name="google-site-verification"> line into the same header-scripts box you’d use for the GA4 snippet (or into Yoast: Yoast SEO → Settings → Site connections → Google, where you paste only the code from the content attribute). Then click Verify. Just remember that if you ever remove the tag, verification lapses.

Submit your Yoast sitemap

This bit is easy, honestly. Yoast SEO generates an XML sitemap automatically once the feature is on (it is by default; check Yoast SEO → Settings → APIs → XML sitemaps). Visit https://yourblog.com/sitemap_index.xml in your browser to confirm it loads and lists post and page sitemaps. Then in Search Console click Sitemaps, type sitemap_index.xml into the “Add a new sitemap” box and click Submit. The status should flip to “Success” within a few minutes to a day. You only ever do this once: Yoast updates the sitemap every time you publish, and Google re-reads it on its own schedule. Sorted.

Not using Yoast? WordPress has a built-in sitemap at /wp-sitemap.xml. Submit whichever one your setup actually serves; submitting both just doubles the noise. Yoast switches the core one off when its own is active.

How to read the Search Console Performance report

Once you’ve got a few weeks of data, Performance → Search results becomes the most valuable page in your whole toolkit. Honestly, if you only ever look at one screen, make it this one. Four numbers sit at the top, and each answers a different question.

• Total clicks: how many people came to your site from Google search in the period. This is your organic traffic, straight from the horse’s mouth.
• Total impressions: how many times any of your pages showed up in results, whether or not anyone clicked. Impressions rise weeks before clicks do, so they’re your early signal that a post is getting noticed.
• Average CTR: clicks divided by impressions. Low CTR with a decent position means your title and meta description aren’t earning the click; rewrite them in Yoast.
• Average position: your average rank across all the queries you appeared for. It’s a blended number and can go “down” when you start ranking for new queries at position 40, so don’t panic about it; look at position per query instead.

Below the chart, flick between the Queries and Pages tabs. The single most useful thing a travel blogger can do, once a month: in Queries, sort by impressions, and look for queries where your position is somewhere between 8 and 20. Those are posts sitting at the bottom of page one or the top of page two. Open the post, make sure the query is answered plainly near the top, add a section if the query hints at something you skipped, add a couple of internal links to it from related posts, and update the date. That routine, more than anything else I’ve seen, is how small blogs climb. The travel blog SEO for beginners post goes deeper on what to change.

Also click the Search appearance tab now and then. It shows whether you’re getting rich results (FAQ, recipe-style snippets) and, as Google keeps rolling out AI features, whether your pages are being pulled into them. Nice to know, not something to lose sleep over.

URL Inspection: getting new posts indexed faster

New blogs get crawled slowly. A brand-new post can sit there unindexed for weeks if you do nothing. The URL Inspection tool at the top of Search Console lets you give Google a nudge. Paste the full URL of your new post into the search bar at the top, press Enter, and wait for the report:

• “URL is on Google”: it’s indexed. Nothing to do. Go write the next one.
• “URL is not on Google”: click Request indexing. Google will queue a crawl, usually within a day or two, sometimes minutes.
• If it says the page is blocked by robots.txt or has a noindex tag, fix that first. On a new WordPress site, the usual culprit is the Settings → Reading → Discourage search engines from indexing this site box still being ticked from setup. Untick it.
• Click Test live URL if you’ve just fixed something and want to check the current version rather than Google’s cached view.

There’s a daily limit on indexing requests per property; Google doesn’t publish the number, but in practice it’s small (around ten a day is the commonly reported figure), so save it for new and substantially updated posts, not for re-submitting the same URL every morning like a nervous parent. Requesting indexing doesn’t guarantee ranking, or even indexing; it just gets Google to have a look. Whether the page STAYS indexed depends on whether it’s worth indexing, which is exactly why the first-post template leans so hard on specifics and first-hand detail.

While you’re in Search Console, look at Indexing → Pages once a month. It lists every URL Google knows about and why any aren’t indexed (“Crawled – currently not indexed”, “Discovered – currently not indexed”, “Duplicate without user-selected canonical” and so on). On a small new blog most of those are harmless: tag archives, attachment pages, feed URLs. What you’re really checking is that your actual posts are in the indexed list. And glance at Experience → Core Web Vitals; if it shows “Poor” URLs on mobile, it’s almost always oversized images, and the image sizing and speed guide is the fix.

A 10-minute weekly analytics routine for a new travel blog

Checking analytics every day on a blog with 30 visitors is a brilliant way to feel bad and change nothing. Once a week is plenty for the first year. Pick a day, set a timer, do this, then close the tab:

1. GA4 → Traffic acquisition, last 28 days vs previous 28. Which channel grew? Note one sentence.
2. GA4 → Pages and screens. Top five posts by views. Any with very low engagement time? Add to your “fix” list.
3. Search Console → Performance, last 3 months. Impressions trending up or down? Any new queries you didn’t expect? Any position 8–20 opportunities?
4. Search Console → URL Inspection for anything you published this week. Request indexing if needed.
5. Write down ONE action for next week: update a post, add internal links, rewrite a title. Then close the tabs. Done.

Common GA4 and Search Console mistakes (and what I’d do differently)

Installing the tag twice

Site Kit plus a pasted snippet, or two analytics plugins, or a theme option plus a plugin. Every pageview counts double, engagement metrics fall apart, and it’s shockingly common on sites I inherit. One tag, one place, and write down where it is.

Following a Universal Analytics tutorial

Loads of these still float about on YouTube. If a guide, video or plugin screenshot shows a tracking ID starting with UA-, a “Behavior → Site Content” menu or a “Bounce rate” column front and center, it predates GA4 and most of it won’t match what you’re looking at. Universal Analytics stopped processing data in 2023. Close the tab. Look for G- IDs and the Reports → Acquisition / Engagement layout I described above.

Counting your own visits

On a new blog, you are a meaningful chunk of your own traffic. Awkward, but true. GA4 lets you define internal traffic by IP under Admin → Data streams → your stream → Configure tag settings → Show all → Define internal traffic, then activate the filter under Admin → Data filters. If your home IP changes a lot, the simpler options are a browser extension that blocks GA on your own domain, or just remembering that the numbers include you while they’re small.

Leaving “Discourage search engines” ticked

People tick it while building the site, forget, and then wonder for three months why Search Console shows zero impressions. I’ve had that exact email more than once. Check Settings → Reading the day you launch. Yoast also flashes a warning at the top of the dashboard when this is on.

Checking every day and reacting to noise

A blog with 20 visits a day will have a 40-visit day and a 9-visit day in the same week for no reason whatsoever. Sound familiar? Compare 28-day windows, or 3-month windows in Search Console. Decisions made on a single day’s data are almost always wrong, and the mood swings aren’t worth it either.

GA4 and Search Console setup checklist

Run down this list once and you’re done with analytics setup for good. Bookmark it.

• Dedicated Google account for the blog created.
• GA4 property created with correct time zone and currency.
• Web data stream created, Enhanced measurement on, Measurement ID (G-…) copied.
• Data retention set to 14 months; own domain added to unwanted referrals.
• Tag installed once, via Site Kit or a header-scripts box; confirmed in Realtime.
• Cookie consent banner and privacy policy in place for EU/UK readers.
• Search Console Domain property verified by DNS TXT (or URL-prefix by HTML tag).
• sitemap_index.xml submitted; status “Success”.
• “Discourage search engines” unticked in Settings → Reading.
• First posts run through URL Inspection and indexing requested.
• Weekly 10-minute review in the calendar.

That’s everything. Forty-five minutes of setup, then ten minutes a week, and you’ll never again have to guess whether your blog is growing. And look, if any of this goes sideways (DNS records are the usual suspect), just email me through the contact page. It’s free, I’m not going to upsell you, and I’d genuinely rather spend ten minutes fixing your verification than have you give up at step six. Now go get that tag installed. Today, not next week.

Frequently asked questions

Do I need both Google Analytics and Search Console for a travel blog?

Yes, both, no way around it. Search Console shows how Google sees your site: queries, impressions, clicks, indexing problems. GA4 shows what visitors do once they land, from any source. Neither one collects data retroactively, so set them up the week you launch, not 'when I have traffic'.

Is Google Analytics 4 free for bloggers?

Yes, completely. GA4 and Search Console are both free with a Google account. The paid Analytics 360 tier is for big enterprises and has nothing to do with a travel blog, so ignore anyone trying to sell you on it.

What is the easiest way to add GA4 to WordPress?

Install the free Site Kit by Google plugin, click Start setup, sign in with Google, and choose your GA4 property and data stream. It places the tag for you and connects Search Console in the same wizard. Ten minutes, tops, and it's what I'd tell almost every beginner to do.

Should I choose a Domain or URL-prefix property in Search Console?

Domain, if you can add a DNS TXT record. It covers www, non-www, http and https in one property and survives theme or host changes, which saves you a proper mess later. Use URL-prefix with the HTML tag method only if you genuinely can't get at DNS. No shame in that.

What sitemap URL do I submit from Yoast SEO?

Submit sitemap_index.xml in Search Console under Sitemaps. Yoast keeps it updated automatically every time you publish, so you only ever do this once. Done.

How long does it take for GA4 and Search Console to show data?

GA4 Realtime shows visitors within about a minute of installing the tag, so that's where to check it's working. Standard GA4 reports and Search Console data typically take 24u201348 hours to start filling in, so don't panic at an empty dashboard on day one.

How do I get a new travel blog post indexed faster?

Paste the post URL into Search Console's URL Inspection bar and click Request indexing. There's a small unpublished daily limit, so save it for new and substantially updated posts, not the same URL every morning. Keep your sitemap submitted and link to the new post from older ones; that does more than people think.

Which GA4 reports should a beginner blogger look at?

Three, and only three for the first year: Traffic acquisition (where visitors come from), Pages and screens (which posts they read and for how long), and Engagement overview (whether they actually read). Check them weekly over a 28-day window, not daily. Daily numbers on a small blog are just noise.