<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://swsblog.stanford.edu/taxonomy/term/169/all" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:og="http://ogp.me/ns#" xmlns:article="http://ogp.me/ns/article#" xmlns:book="http://ogp.me/ns/book#" xmlns:profile="http://ogp.me/ns/profile#" xmlns:video="http://ogp.me/ns/video#" xmlns:product="http://ogp.me/ns/product#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
  <channel>
    <title>SEO</title>
    <link>https://swsblog.stanford.edu/taxonomy/term/169/all</link>
    <description></description>
    <language>en</language>
     <atom:link href="https://swsblog.stanford.edu/taxonomy/term/169/all/feed" rel="self" type="application/rss+xml" />
      <item>
    <title>How to tell Google about your Stanford Sites website</title>
    <link>https://swsblog.stanford.edu/blog/how-tell-google-about-your-stanford-sites-website</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p class=&quot;summary&quot;&gt;You&#039;ve put time into creating your &lt;a href=&quot;http://sites.stanford.edu&quot;&gt;Stanford Sites&lt;/a&gt; website, so you&#039;ll probably want Google (and other search engines) to know about it. One of the ways to get this done is by submitting your website sitemap. This blog post will walk you through how to claim ownership of your Stanford Sites website, then submit the website to Google for indexing. &lt;/p&gt;
&lt;p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 17 Aug 2018 00:28:39 +0000</pubDate>
 <dc:creator>Alyssa Hislop</dc:creator>
 <guid isPermaLink="false">756 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Writing for the Web #1: Calls to Action</title>
    <link>https://swsblog.stanford.edu/blog/writing-web-1-calls-action</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p class=&quot;summary&quot;&gt;Get people more engaged in your content! With this post, I&#039;ll outline two basic guidelines for writing good Calls to Action to lead users through your site.&lt;/p&gt;
&lt;h2&gt;What is a Call to Action?&lt;/h2&gt;
&lt;p&gt;A Call to Action is a snippet of text with a link, sometimes styled as a button or with an arrow after it. Use Calls to Action when you want to get your readers to do something — whether it&#039;s to click through to another page, download a document, or even purchase something. &lt;span&gt;A few basic academic examples might be: &lt;/span&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Tue, 16 Jul 2013 18:17:46 +0000</pubDate>
 <dc:creator>Linnea Ann Williams</dc:creator>
 <guid isPermaLink="false">207 at https://swsblog.stanford.edu</guid>
  </item>
  </channel>
</rss>
