<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Integrations on Emet CMS</title>
		<link>https://docs.emetcms.com/integrations/</link>
		<description>Recent content in Integrations on Emet CMS</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
			<copyright>Documentation site content for Emet CMS. Theme based on [Hugo Book](https://github.com/alex-shpak/hugo-book) by [Alex Shpak](https://github.com/alex-shpak).
</copyright>
		
		
			<atom:link href="https://docs.emetcms.com/integrations/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>GitHub App</title>
				<link>https://docs.emetcms.com/integrations/github-app/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://docs.emetcms.com/integrations/github-app/</guid>
				<description>&lt;p&gt;Emet needs a GitHub token to read and write your repository. The quick way to get one is a personal access token, and Emet still accepts those, but asking every editor to generate a PAT with the right scopes is a faff and they expire at awkward moments. A GitHub App gives you a &lt;strong&gt;Sign in with GitHub&lt;/strong&gt; button instead, with short-lived tokens that Emet refreshes itself.&lt;/p&gt;&#xA;&lt;p&gt;Under the hood this is the OAuth authorization code flow with PKCE. The browser sends people to GitHub, GitHub sends them back with a code, and a Pages Function at &lt;code&gt;/api/github/token&lt;/code&gt; swaps the code for a token, adding the app&amp;rsquo;s client secret on the way. The secret never reaches the browser.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Google Search Console</title>
				<link>https://docs.emetcms.com/integrations/google-search-console/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://docs.emetcms.com/integrations/google-search-console/</guid>
				<description>&lt;p&gt;The SEO panel can tell you whether a post ticks the boxes, but not whether anyone&amp;rsquo;s finding it. Search Console can. With this integration connected, the bottom of the SEO tab shows the page&amp;rsquo;s clicks, impressions, average click-through rate and average position for the last 28 days, and a table of the queries that brought people there, so you can see which words are already working before you decide what to optimise.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
