Upcoming LunaMetrics Seminars
Los Angeles - Anaheim, Sep 8-12 Washington DC, Sep 22-26 Boston, Oct 6-10 Chicago, Oct 20-24

Showing Page Titles & URLs in Google Analytics





Blue Light Bulb Sometimes when presenting a report to someone else, you may want to display a list of pages as Page Titles instead of URLs.  But you still want to filter the list to show only certain pages.  And you want to filter the list to only show pages based on the URL. In this screenshot, I am displaying a report by URL and as the Secondary Dimension I have selected Page Title.  The filter at the bottom of the report works on the First Column and I have filtered the report to a particular subdirectory.

So far this looks pretty straight forward, right?

THE CATCH:
The catch is, in GA, there is no option to select Page Title as a Secondary Dimension in the URL report.

url list

This means that if you want to display the pages by Page Title for only a sub-directory, you’d have to come up with a very convoluted filter to filter in every page title in that subdirectory and at the same time remove unwanted positive matches from other sub-directories.

So how did I get URL and Page Title to show up in the same report?

The trick is in using a URL parameter called “segkey” which you add to the URL in the address bar for the report. For reference, I’ve included the report URL below  (Note that I xxx’d out the ID for the profile):

https://www.google.com/analytics/reporting/top_content?id=xxxxxx&pdr=20100515-20100614&cmp=average&trows=10&gdfmt=nth_day&rpt=TopContentReport&segkey=request_uri|page_title&tab=0&tchcol=0&tst=0&tscol=v0

Step 1: Generate your Top Content Report
Step 2: Copy and Paste &segkey=request_uri|page_title into the url in the query parameter section of the URL (amidst the other & parameters)
Step 3: Press enter and enjoy your report.

Other reasons to do this

There are a couple of reasons, from an SEO perspective, that you may want to show both the page URI and page title together.

1. Find duplicate title tags – If you’re looking at a specific section of your site, like in the example above, you can quickly see how targeted your title tags are. You might even find duplicate title tags. In the example above, you can see we have two pages with the same title tag – #4 and #8. Each page on your site should have a different title tag, and this gives you the opportunity to be more specific and target more long-tail search terms.

2. Monitor & Measure – If you’ve changed the title tag on a page, you can filter to contain just the URI for that page, then show a month before and a month after the change to see if traffic to that page has increased or decreased.

Thanks to Jim for the “Other reasons to do this” section, and thanks to Christina for helping me to rewrite parts of the post.

http://www.lunametrics.com/blog/2010/07/15/showing-page-titles-url-google-analytics/

21 Responses to “Showing Page Titles & URLs in Google Analytics”

Des Traynor says:

Nice work, so very useful.

Could you use a hack like this to extract Referrer URI.

One piece of info I’ve always been keep to get is “Referrer URI” following by “Requested URI”.

E.g. if this blog post sends 3 visitors to my site, I’d like to know
a) That it was this blog post
and
b) Which page on my site it linked to.

Do you reckon this is possible?

Regards,
Des

John says:

I don’t know if that is possible or not.

GA seems to keep the referrer URL in 2 parts, the Source and the Referral Path.

But since those are both visit level dimensions, I’m not sure that they would pair well with pageview level dimensions.

It might be possible to do something with a custom report where you started showing Landing Page and drilled down to see Source + Referral Path. But this isn’t something I can remember doing.

If I get some time I’ll see if I can give that a try. Or if you end up trying it out, let us know how it worked (or didn’t).

John

Hello,

Where can I find the the query parameter section of the URL (amidst the other & parameters)? I am logged in to GA as an administrator and am basically new at this.

Any help is much appreciated!

Laura

Step 1: Generate your Top Content Report
Step 2: Copy and Paste &segkey=request_uri|page_title into the url in the query parameter section of the URL (amidst the other & parameters)
Step 3: Press enter and enjoy your report.

John says:

A query parameter is the part of the URL that is after the path. The first query parameter is denoted by a question mark (?) and subsequent query parameters are denoted by an ampersand (&).

Eric says:

Sub-directories… for some reason I can’t seem to get sub-directories to work.. I have used custom filters, includes, you name it I have probably tried it..

The challenge is that you can’t use the ^ in the standard filters which is the way that Google suggest. You can use it in Custom Filters but those dont seem to work either.. any assistance on this single item?

John says:

Eric,

This post isn’t about sub-directories or regular expressions/custom filters. So I’m not sure what you’re trying to do.

Sorry,

John

Is there any way to make this hack work with the Product SKU ecommerce report? It would be very helpful to show SKU and product name (page title) in the same report. Thanks!

John says:

Christian,

I don’t know. I haven’t tried that. But it would probably just be a matter of going to that report and using the right “segkey” value in the URL.

Alternatively, you can probably combine them into the same field with a Custom -> Advanced profile filter. (But only for data going forward).

John – I was thinking the same thing about using the right”segkey” value. Is there a way to find out how these are formatted for different variables?

John says:

The only way I know is to segment by the thing your interested in. Save to dashboard. Then look in the “view report” link that is on the dashboard view of that saved report.

Thanks! That’s all I needed to know. In case you’re interested the segkey to display product name and SKU in the same report is:

&segkey=product_name|product_code

gaSniper says:

any idea how to get this to work on thew new version of GA? The URL parameters are now different.

sonic says:

In new version of GA , WHERE IS “PAGE TITLE” ?
Thanks.

Jon says:

Hi all

This works in the new version using the following
https://www.google.com/analytics/web/#report/content-pages/a526168w877213p857886/%3Fexplorer-segmentExplorer.segmentId%3Danalytics.pagePath%26explorer-table.secSegmentId%3Danalytics.pageTitle

The important parts are
analytics.pagePath – the path (request_URI in the original example)
analytics.pageTitle – the page title (page_title in the original example)
You can also swap these to segment the title by the path.
I tried this with versions of request_URI eg requestURI, but this seems to have been usurped by pagePath

Note: if you go straight to the content report, there are no segments in the url originally. If you click to page title in the report you will see analytics.pageTitle appear in the url. If you click on pages you will see pagePath appear in the url – with this information I created the above url.

hope this helps!
cheers
Jon

The last part (analytics.pagePath) pulls

The new version calls the page pagePath now – requestURI seems to be for landing page.

Jon says:

here is a video of changing the url in the new version

metricks.org/articles/changing-urls-google-analytics/

cheers
Jon

In the new analytics, you can use a custom report and get this list very easily…
seobywebmechanix.com/how-to-use-analytics-to-map-urls-with-page-titles/

Also, Google webmaster tools tells you all your duplicate title (& description) tags.

Sarah Ng says:

Hi all,

Would you kindly help me as I have recently add the following in the script:

_gaq.push(['siteTracker._trackPageview', 'PageName']);

Is it correct that I won’t able to see the FULL URL in the PAGE report anymore and to do the URL filering using paramter?

Thanks and look forward to any kind help!

@Sarah -

Whatever you specify in the ‘PageName’ parameter is how it will appear in the content reports. For example, if you have the following:

_gaq.push(['siteTracker._trackPageview', 'http://www.example.com/some-page.html'])

When you look at your content reports, you’ll see:
/http://www.example.com/some-page.html

(GA assumes you’re setting the page path, hence the forward slash at the beginning)

Now, if the code on your page is exactly as you put above (you are literally setting the page path to ‘PageName’) then yes, you will not be able to see the full URL of the requested page.

wannee says:

want to show page

Thanks for your helpful article!

What’s Taking place i am new to this, I stumbled upon this I have discovered It absolutely useful and it has aided me out loads. I hope to give a contribution & aid different customers like its helped me. Good job.