{
  "location": "Fort Lauderdale, FL, United States",
  "title": "RN Per Diem Nurse",
  "city": "Fort Lauderdale",
  "state": "FL",
  "zip": "33336",
  "country": "United States",
  "job_type": "",
  "posted_at": "2018-04-21",
  "job_reference": "63_Apr47387",
  "company": "HealthTrust Workforce Solutions",
  "mobile_friendly_apply": "No",
  "category": "Per Diem",
  "html_jobs": "Yes",
  "url": "https://click.appcast.io/track/oan6v1?cs=ae4&exch=1a&bid=TEz0xVerpiuhxLt0LS4mUA==",
  "body": "HealthTrust Workforce Solutions offers Registered Nurses (RNs) job opportunities in leading healthcare facilities across the country. The specialties we staff include ICU, Critical Care, Med/Surg, Telemetry, ER, PACU, Labor & Delivery, and more!<p> With regional and satellite recruitment offices nationwide, we work around the clock to provide the best support for our Per Diem Nurses. We offer flexible scheduling, meaning you get first preference on where and when to work, first call / last cancelled and one of the most competitive compensation packages in the market.<p> If you are a registered nurse (RN) and are interested in learning more about our careers, please fill out the form below and one of our skilled recruiters will contact you shortly.<p> <strong>Please note that certain requirements must be met in order to be eligible to work per diem with HealthTrust Workforce Solutions.</strong> <li>Graduate from an accredited nursing school   <li>Minimum of one year acute care experience in a hospital setting   <li>Current State Nursing License   <li>All appropriate certifications for the position to which you are applying",
  "cpa": 5.831,
  "cpc": 0.24
}

<script type="application/ld+json"> {
  "@context" : "http://schema.org/",
  "@type" : "JobPosting",
  "title" : "Fitter and Turner",
  "description" : "<p>Widget assembly role for pressing wheel assemblies.</p>
    <p><strong>Educational Requirements:</strong> Completed level 2 ISTA
    Machinist Apprenticeship.</p>
    <p><strong>Required Experience:</strong> At
    least 3 years in a machinist role.</p>",
  "identifier": {
    "@type": "PropertyValue",
    "name": "MagsRUs Wheel Company",
    "value": "1234567"
  },
  "datePosted" : "2017-01-18",
  "validThrough" : "2017-03-18T00:00",
  "employmentType" : "CONTRACTOR",
  "hiringOrganization" : {
    "@type" : "Organization",
    "name" : "MagsRUs Wheel Company",
    "sameAs" : "http://www.magsruswheelcompany.com",
    "logo" : "http://www.example.com/images/logo.png"
  },
  "jobLocation" : {
    "@type" : "Place",
    "address" : {
      "@type" : "PostalAddress",
      "streetAddress" : "555 Clancy St",
      "addressLocality" : "Detroit",
      "addressRegion" : "MI",
      "postalCode" : "48201",
      "addressCountry": "US"
    }
  },
  "baseSalary": {
    "@type": "MonetaryAmount",
    "currency": "USD",
    "value": {
      "@type": "QuantitativeValue",
      "value": 40.00,
      "unitText": "HOUR"
    }
  }
}
</script>

* Max sitemap size: 50mb uncompressed and 50,000 urls.
  * Can break into multiple site maps if those limits are exceeded. We can also create what is effectively a sitemap manifest [here](https://support.google.com/webmasters/answer/75712)
* It looks like XML is the weapon of choice. This is the [XML sitemap protocol](https://www.sitemaps.org/protocol.html)
  * There aren't many things to reference really. Your sitemap would include entries for each URL and some metadata about them. ~~If each leaf page has references to related searches (visible or otherwise?), then the sitemap would allow us to indicate a `priority` among the urls. That priority could follow some ranking, or be arbitrary, or just be theJobPostYouAreOn > theJobsInMetaData.~~The docs make this seem less useful for us actually. Priority is relative to the other urls on your site. For us, this would only really apply if we were building a homepage at something like `starspawn.blowjobs.com/jobs` that had a big list of jobs + links.
  * At the very least, having a sitemap would allow us to clearly indicate to google/crawlers the last-modified date and change-frequency. This could be useful for our system because it will be updating relatively often, at least compared to most other systems it seems.
  * `changeFreq` seems like the truly relevant field in sitemaps for our present needs. It is basically giving a suggestion to crawlers for how often they should crawl your site. That seems like something we would want if we are going to be pushing updates to jobs, at least if the URL to it remains constant (doesn't seem likely). If new updates to job postings create new URLs, then this is useless, really.

* If we have a site that is basically just _a job_, in that it has some information bout it plus links to the employer and job posting itself, what benefit does a sitemap provide? I suppose we may want the company's URL made more available via the sitemap as I think it would help us when someone is searching jobs for a specific company.
* Well, turns out we probably do want to build a sitemap for our job pages either way. It is telling Google to pretty plz index our page, and should be super straight forward to make for any given job post.

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
      <loc>https://us-central1-starspawn-201921.cloudfunctions.net/render?jobId=63_Apr47792/</loc>
      <lastmod>2018-05-13</lastmod>
      <changefreq>daily</changefreq>
      <priority>0.8</priority>
   </url>
</urlset>