<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>KOAH</title>
	<atom:link href="https://www.koah.dk/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.koah.dk</link>
	<description>Team up med ægte SEO warriors fra KOAH</description>
	<lastBuildDate>Tue, 09 Jun 2020 17:42:10 +0000</lastBuildDate>
	<language>da-DK</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.3.4</generator>
	<item>
		<title>Pagination</title>
		<link>https://www.koah.dk/kb/pagination/</link>
				<pubDate>Tue, 09 Jun 2020 09:14:50 +0000</pubDate>
		<dc:creator><![CDATA[martin]]></dc:creator>
				<category><![CDATA[Knowledge base]]></category>

		<guid isPermaLink="false">https://www.koah.dk/?p=186</guid>
				<description><![CDATA[<p>Contents Relationship: next/prev Canonical Page break with links Infinite scroll Index status You can implement pagination in different ways. Which one that suits you best depends on the search volume of your products. You need to consider if you want to transfer internal link value from category pages and brand pages to product pages. In &#8230; <a href="https://www.koah.dk/kb/pagination/" class="more-link">Continue reading <span class="screen-reader-text">Pagination</span></a></p>
<p>The post <a rel="nofollow" href="https://www.koah.dk/kb/pagination/">Pagination</a> appeared first on <a rel="nofollow" href="https://www.koah.dk">KOAH</a>.</p>
]]></description>
								<content:encoded><![CDATA[
<h2>Contents</h2>



<ol><li><a href="#relationship">Relationship: next/prev</a></li><li><a href="#canonical">Canonical</a></li><li><a href="#breaks">Page break with links</a></li><li><a href="#infinite">Infinite scroll</a></li><li><a href="#index">Index status</a></li></ol>



<p>You can implement pagination in different ways. Which one that suits you best depends on the search volume of your products.</p>



<p>You
need to consider if you want to transfer internal link value from category
pages and brand pages to product pages. In your case, I recommend doing it as
there is a lot of direct searches for your products.</p>



<p>Therefore,
you should do the following:</p>



<p>Based
on: <a href="https://www.domain.dk/category/">https://www.domain.dk/category/</a></p>



<p>For
page 1, page 2, page 3, etc. you can use this URL structure:</p>



<ul><li>Page 1 – <a href="https://www.domain.dk/category/">https://www.domain.dk/category/</a></li><li>Page 2 – <a href="https://www.domain.dk/category/page-2/">https://www.domain.dk/category/page-2/</a></li><li>Page 3 – <a href="https://www.domain.dk/category/page-3/">https://www.domain.dk/category/page-3/</a></li></ul>



<p>Or:
</p>



<ul><li>Page 1 – <a href="https://www.domain.dk/category/">https://www.domain.dk/category/</a></li><li>Page 2 – <a href="https://www.domain.dk/category/?page=2/">https://www.domain.dk/category/?page=2/</a></li><li>Page 3 – <a href="https://www.domain.dk/category/?page=3/">https://www.domain.dk/category/?page=3/</a></li></ul>



<p>It is important that you do not create links to <em>page-1</em> or <em>page=1</em> as they do not exist. The first page in the series is always just: <a href="https://www.domain.dk/category/">https://www.domain.dk/category/</a>.</p>



<p>If an URL does not exist, it needs to return a 404-status code. If your series consists of three pages and page 4 is requested (<a href="https://www.domain.dk/category/page-4/">https://www.domain.dk/category/page-4/</a>) it has to return a 404-status code. </p>



<h3 id="relationship">Relationship: next/prev</h3>



<p>Google does not use <em>rel=next/prev</em> anymore but other search engines might. If you choose to implement the <em>rel</em>-tag, it is done as follows:</p>



<p>The <em>rel</em>-tag is inserted between<em> &lt;head&gt;&lt;/head&gt;</em>.</p>



<p><strong>Example</strong><br>If you have three pages in the series, the implementation must look like this:</p>



<p>Page
1: <a href="https://www.domain.dk/category/">https://www.domain.dk/category/</a>
refers to the next page:</p>



<pre class="wp-block-preformatted">&lt;link rel="next" href="<a href="https://www.domain.dk/category/page-2/">https://www.domain.dk/category/page-2/</a>" /&gt;</pre>



<p>Page
2 refers to the previous page and the next page:</p>



<pre class="wp-block-preformatted">&lt;link rel="prev" href="<a href="https://www.domain.dk/category/">https://www.domain.dk/category/</a>" /&gt;</pre>



<pre class="wp-block-preformatted">&lt;link rel="next" href="<a href="https://www.domain.dk/category/page-3/">https://www.domain.dk/category/page-3/</a>" /&gt;</pre>



<p>As
page 3 is the last page in the series, it only refers to the previous page:</p>



<pre class="wp-block-preformatted">&lt;link rel="prev" href="<a href="https://www.domain.dk/category/page-2/">https://www.domain.dk/category/page-2/</a>" /&gt;</pre>



<h3 id="canonical">Canonical</h3>



<p>You need to have a self-referring canonical tag on all pages, i.e. page 2 has a canonical tag to page 2, page 3 to page 3, etc.</p>



<h3 id="breaks">Page break with links</h3>



<p>To ensure that Google crawls all pages, it is important to always have a
standard <em>&lt;a href=””&gt;Anchor&lt;a&gt;</em> link to all pages in a
pagination series:</p>



<figure class="wp-block-image size-large"><img src="https://www.koah.dk/wp-content/uploads/2020/06/seo-pagination-rel-prev-next1-1024x273.png" alt="How to use self-canonical in pagination" class="wp-image-190" srcset="https://www.koah.dk/wp-content/uploads/2020/06/seo-pagination-rel-prev-next1-1024x273.png 1024w, https://www.koah.dk/wp-content/uploads/2020/06/seo-pagination-rel-prev-next1-300x80.png 300w, https://www.koah.dk/wp-content/uploads/2020/06/seo-pagination-rel-prev-next1-768x205.png 768w, https://www.koah.dk/wp-content/uploads/2020/06/seo-pagination-rel-prev-next1-1536x410.png 1536w, https://www.koah.dk/wp-content/uploads/2020/06/seo-pagination-rel-prev-next1.png 1600w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption>Credits:  searchenginejournal.com</figcaption></figure>



<h3 id="infinite">Infinite scroll</h3>



<p>If you use infinity scroll, use <a href="https://developer.mozilla.org/en-US/docs/Web/API/History_API" target="_blank" rel="noreferrer noopener" aria-label=" (opens in a new tab)">History API</a> for page breaks. This means that your URL automatically changes to page 2, page 3, etc. as the user scrolls down the page. You can see an example here: <a href="https://scrollsample.appspot.com/items" target="_blank" rel="noreferrer noopener" aria-label=" (opens in a new tab)">https://scrollsample.appspot.com/items</a> </p>



<p>Make
sure that:</p>



<ul><li>The page number always correspond to the content presented.</li><li>All pages of the series can be accessed directly so Google can crawl and index the content.</li><li>Lazy load is implemented so all relevant content is loaded in the visible viewport.</li><li><a href="https://developers.google.com/web/updates/2016/04/intersectionobserver" target="_blank" rel="noreferrer noopener" aria-label=" (opens in a new tab)">IntersectionObserver API</a> is used to support paginated loading in the case of infinity scroll. Do not use scroll events. This is the most effective way to make Googlebot follow the invisible components.</li></ul>



<p>To make sure that the above is implemented correctly, you should test the configuration locally by using <a href="https://github.com/puppeteer/examples/blob/master/lazyimages_without_scroll_events.js" target="_blank" rel="noreferrer noopener" aria-label=" (opens in a new tab)">Puppeteer script</a>.</p>



<p>Source: <a href="https://webmasters.googleblog.com/2014/02/infinite-scroll-search-friendly.html" target="_blank" rel="noreferrer noopener" aria-label=" (opens in a new tab)">https://webmasters.googleblog.com/2014/02/infinite-scroll-search-friendly.html</a><br>Source: <a href="https://developers.google.com/search/docs/guides/lazy-loading" target="_blank" rel="noreferrer noopener" aria-label=" (opens in a new tab)">https://developers.google.com/search/docs/guides/lazy-loading</a></p>



<h3 id="index">Index status</h3>



<p>Many websites use a <em>noindex, follow</em> tag on page 2, page 3, etc. to avoid them being indexed in Google. However, this means that eventually, they stop transferring internal link value to the products on the pages. Read more here: <a href="https://www.seroundtable.com/google-long-term-noindex-follow-24990.html" target="_blank" rel="noreferrer noopener" aria-label=" (opens in a new tab)">https://www.seroundtable.com/google-long-term-noindex-follow-24990.html</a>. </p>



<p>Therefore, all pages in the series (those you want to transfer link value) should have an <em>index, follow</em> tag. By doing this, page 2, page 3, etc. can – just as <a href="https://www.domain.dk/category/">https://www.domain.dk/category/</a> – be shown in Google on different keywords. However, we can assure that <a href="https://www.domain.dk/category/">https://www.domain.dk/category/</a> is the primary result in Google by doing the following:</p>



<h4>Metadata</h4>



<p>To avoid duplicate metadata, these should be automatically generated for page 2, page 3, etc.</p>



<p><strong>Title tag page 2:</strong><br>Page 2 of category | Domain.dk</p>



<p><strong>Description page 2:</strong><br>Page 2 of category. Shows 40 to 80 out of 200 products. Category in all price ranges.</p>



<h4>Onsite text</h4>



<p>Page 1 contains a good onsite text. Page 2, page 3, etc. do not have onsite texts.</p>



<h4>Internal links</h4>



<p>Internal links from other pages should always go to the first page of a
series, that is <a href="https://www.domain.dk/category/">https://www.domain.dk/category/</a>.</p>
<p>The post <a rel="nofollow" href="https://www.koah.dk/kb/pagination/">Pagination</a> appeared first on <a rel="nofollow" href="https://www.koah.dk">KOAH</a>.</p>
]]></content:encoded>
										</item>
		<item>
		<title>Image sitemap</title>
		<link>https://www.koah.dk/kb/image-sitemap/</link>
				<pubDate>Wed, 15 Apr 2020 21:08:17 +0000</pubDate>
		<dc:creator><![CDATA[martin]]></dc:creator>
				<category><![CDATA[Knowledge base]]></category>

		<guid isPermaLink="false">https://www.koah.dk/?p=178</guid>
				<description><![CDATA[<p>We recommend using an image sitemap to increase the likelihood that your images can be found in Image Search results on Google. Additionally, you can use Google image extensions for sitemaps to give Google more information about the images available on your pages. Image sitemap information helps Google discover images that we might not otherwise &#8230; <a href="https://www.koah.dk/kb/image-sitemap/" class="more-link">Continue reading <span class="screen-reader-text">Image sitemap</span></a></p>
<p>The post <a rel="nofollow" href="https://www.koah.dk/kb/image-sitemap/">Image sitemap</a> appeared first on <a rel="nofollow" href="https://www.koah.dk">KOAH</a>.</p>
]]></description>
								<content:encoded><![CDATA[
<p>We
recommend using an image sitemap to increase the likelihood that your images
can be found in Image Search results on Google.</p>



<p>Additionally, you can use Google image extensions for sitemaps to give Google more information about the images available on your pages. Image sitemap information helps Google discover images that we might not otherwise find (such as images your site reaches with JavaScript code), and allows you to indicate images on your site that you want Google to crawl and index.</p>



<p>Source: <a href="https://support.google.com/webmasters/answer/178636?hl=en">https://support.google.com/webmasters/answer/178636?hl=en</a></p>
<p>The post <a rel="nofollow" href="https://www.koah.dk/kb/image-sitemap/">Image sitemap</a> appeared first on <a rel="nofollow" href="https://www.koah.dk">KOAH</a>.</p>
]]></content:encoded>
										</item>
		<item>
		<title>URL structure</title>
		<link>https://www.koah.dk/kb/url-structure/</link>
				<pubDate>Tue, 14 Apr 2020 21:45:17 +0000</pubDate>
		<dc:creator><![CDATA[martin]]></dc:creator>
				<category><![CDATA[Knowledge base]]></category>

		<guid isPermaLink="false">https://www.koah.dk/?p=174</guid>
				<description><![CDATA[<p>Lav så korte url’er som muligt. De skal dog stadig forklare, hvad url’en indeholder. Brug ikke specialtegn eller store bogstaver. Brug bindestreg til mellemrum – ikke underscores. Hvis det er muligt, så undgå parametre som fx: ?color=12. Det fortæller intet om, hvad url’en indeholder. Brug vigtige søgeord i jeres url’er.</p>
<p>The post <a rel="nofollow" href="https://www.koah.dk/kb/url-structure/">URL structure</a> appeared first on <a rel="nofollow" href="https://www.koah.dk">KOAH</a>.</p>
]]></description>
								<content:encoded><![CDATA[
<ul><li>Lav så korte url’er som muligt. De skal dog
stadig forklare, hvad url’en indeholder.</li><li>Brug ikke specialtegn eller store bogstaver.</li><li>Brug bindestreg til mellemrum – ikke underscores.</li><li>Hvis det er muligt, så undgå parametre som fx:
?color=12. Det fortæller intet om, hvad url’en indeholder.</li><li>Brug vigtige søgeord i jeres url’er.</li></ul>
<p>The post <a rel="nofollow" href="https://www.koah.dk/kb/url-structure/">URL structure</a> appeared first on <a rel="nofollow" href="https://www.koah.dk">KOAH</a>.</p>
]]></content:encoded>
										</item>
		<item>
		<title>Redirects</title>
		<link>https://www.koah.dk/kb/redirects/</link>
				<pubDate>Tue, 14 Apr 2020 21:41:16 +0000</pubDate>
		<dc:creator><![CDATA[martin]]></dc:creator>
				<category><![CDATA[Knowledge base]]></category>

		<guid isPermaLink="false">https://www.koah.dk/?p=167</guid>
				<description><![CDATA[<p>Contents 301 redirects Absolute URIs 301 redirects 301-redirecter url’er med store bogstaver til url’er med små bogstaver. Det vil sige, at www.domæne.dk/Url 301-redirecter til www.domæne.dk/url 301-redirecter url’er med eller uden skråstreg til den korrekte version. Lige nu kører I en blanding, så I har både www.domæne.dk/url samt www.domæne.dk/url/. Her skal I vælge en version og &#8230; <a href="https://www.koah.dk/kb/redirects/" class="more-link">Continue reading <span class="screen-reader-text">Redirects</span></a></p>
<p>The post <a rel="nofollow" href="https://www.koah.dk/kb/redirects/">Redirects</a> appeared first on <a rel="nofollow" href="https://www.koah.dk">KOAH</a>.</p>
]]></description>
								<content:encoded><![CDATA[
<h2>Contents</h2>



<ol><li><a href="#301-redirects">301 redirects</a></li><li><a href="#absolute-uris">Absolute URIs</a></li></ol>



<h3 id="301-redirects">301 redirects</h3>



<p>301-redirecter url’er med store bogstaver til url’er med små
bogstaver. Det vil sige, at <a href="http://www.domæne.dk/Url">www.domæne.dk/Url</a>
301-redirecter til <a href="http://www.domæne.dk/url">www.domæne.dk/url</a></p>



<ul><li>301-redirecter url’er med eller uden skråstreg til den korrekte version. Lige nu kører I en blanding, så I har både <a href="http://www.domæne.dk/url">www.domæne.dk/url</a> samt <a href="http://www.domæne.dk/url/">www.domæne.dk/url/</a>. Her skal I vælge en version og sørge for, at I konsekvent linker og 301-redirecter til den samme version. Vælger I <a href="http://www.domæne.dk/url">www.domæne.dk/url</a>, vil <a href="http://www.domæne.dk/url/">www.domæne.dk/url/</a> 301 redirecte til <a href="http://www.domæne.dk/url">www.domæne.dk/url</a>.</li><li>Url’er med parametre har kun et canonical tag til originalen. Så <a href="http://www.domæne.dk/url?parametre=1">www.domæne.dk/url?parametre=1</a> har et canonical tag til <a href="http://www.domæne.dk/url">www.domæne.dk/url</a>. Har I en url med parametre, der skal indekseres i Google, skal den ikke indeholde et canonical tag. </li></ul>



<p>Ved url’er som <a href="http://www.domæne.dk/url-344">www.domæne.dk/url-344</a> returneres der en 404 status kode, så lige meget hvilken kombination man laver af url’en, laver den enten en 301-redirect, har et canonical tag til sig selv eller returnerer en 404 statuskode.</p>



<h3 id="absolute-uris">Absolute URIs</h3>



<p>The field value consists of a single absolute URI.<br>Source: <a rel="noreferrer noopener" target="_blank" href="https://tools.ietf.org/html/rfc2616#section-14.30">https://tools.ietf.org/html/rfc2616#section-14.30</a></p>
<p>The post <a rel="nofollow" href="https://www.koah.dk/kb/redirects/">Redirects</a> appeared first on <a rel="nofollow" href="https://www.koah.dk">KOAH</a>.</p>
]]></content:encoded>
										</item>
	</channel>
</rss>
