PageSourceSearch

https://skillihire.com/

html skillihire.com collected 2026-10-02 01:43:22 UTC 3,761 bytes, 55 lines download raw bytes

1<!doctype html>
2<html lang="en">
3  <head>
4    <meta charset="UTF-8" />
5    <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=5.0, viewport-fit=cover" />
6    <meta name="theme-color" content="#3b82f6" />
7    <meta name="apple-mobile-web-app-capable" content="yes" />
8    <meta name="apple-mobile-web-app-status-bar-style" content="default" />
9    <meta name="mobile-web-app-capable" content="yes" />
10    <link rel="icon" href="/favicon.png" type="image/png" />
11    <title>SkilliHire Australia – AI Development, Consulting & Automation (NSW)</title>
12    <meta name="description" content="Australian AI solutions company serving clients nationwide, with offices in Sydney and Orange NSW. AI development, machine learning, predictive maintenance and automation for enterprise, mining, education and SMEs across Sydney, Melbourne, Brisbane, Perth and regional Australia." />
13    <meta name="author" content="SkilliHire" />
14    <meta name="keywords" content="AI development Australia, AI consulting Australia, AI company NSW, machine learning Australia, predictive maintenance Australia, AI automation Sydney, AI solutions Melbourne, industrial AI mining Australia, AI training Australia, ACARA homeschooling AI" />
15    <meta name="geo.region" content="AU-NSW" />
16    <meta name="geo.placename" content="Orange, New South Wales" />
17    <meta name="geo.position" content="-33.2833;149.1" />
18    <meta name="ICBM" content="-33.2833, 149.1" />
19
20    <meta property="og:title" content="SkilliHire — AI Development & Custom Software, Australia" />
21    <meta property="og:description" content="We build the AI and software your business actually runs on. Sydney and Orange NSW, serving clients Australia-wide." />
22    <meta property="og:locale" content="en_AU" />
23    <meta property="og:type" content="website" />
24    <meta property="og:site_name" content="SkilliHire" />
25    <meta property="og:image" content="https://www.skillihire.com/og-image-v2.jpg" />
26    <meta property="og:image:width" content="1200" />
27    <meta property="og:image:height" content="630" />
28    <meta property="og:image:alt" content="SkilliHire — Australian AI development and custom software company" />
29
30    <!-- twitter:site is deliberately absent: twitter.com/SkilliHire returns 404,
31         so the handle we were claiming does not exist. The card still renders
32         from twitter:card and the og: tags. Restore this line, and add the URL
33         to src/lib/socialProfiles.ts, once an account exists. -->
34    <meta name="twitter:card" content="summary_large_image" />
35    <meta name="twitter:image" content="https://www.skillihire.com/og-image-v2.jpg" />
36
37    <!--
38      No canonical or og:url here on purpose.
39
40      This file is the SPA fallback for every route, so a hardcoded canonical is
41      served on /products/evolamate, /locations/sydney and every other URL —
42      telling a crawler that all of them are duplicates of the homepage. With the
43      tag absent, Google falls back to the requested URL, which is correct.
44
45      Prerendered pages (npm run build:seo) each carry their own canonical baked
46      in, and useSEO writes one at runtime for anything served from this shell.
47    -->
48    
48<script type="module" crossorigin src="/assets/index-DMpD5zQ4.js"></script>
48
49    <link rel="stylesheet" crossorigin href="/assets/index-CVDhzJfm.css">
50  
50<script defer src="/~flock.js" data-proxy-url="/~api/analytics"></script>
50<meta name="twitter:title" content="SkilliHire — AI Development &amp; Custom Software, Australia"><meta name="twitter:description" content="We build the AI and software your business actually runs on. Sydney and Orange NSW, serving clients Australia-wide."></head>
51
52  <body>
53    <div id="root"></div>
54  </body>
55</html>

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.