It operates like a ~2017 brochure site in a 2026 AI-search world.
Today technitask.com works as a D-grade web presence — weak across the eight things that decide whether customers and AI engines pick you.
Indexable and stable at the base, but generic one-word titles, a sitewide-duplicate meta description, missing canonicals, and zero structured data leave easy ranking and rich-result wins on the table — and the lack of schema plus a JS-only contact page make the site hard to cite in AI search.
The biggest drags are Content Quality & E-E-A-T (F), AI Search (AEO) (D), and Message & Positioning (D). Closing those first is worth about +19 on its own — on the way to a projected A− · 89 once the full plan is done.
Whether search engines and AI can reach, read, and surface the site at all.
Indexable, but one-word titles, a duplicate meta description, and missing canonicals leave easy ranking wins on the table.
What it costs you · Anyone who types your domain without 'www' — from a card, an email, or memory — gets a dead page.
Typing technitask.com (without 'www') fails to load, while www.technitask.com works. Anyone who enters the bare domain — from a business card, an email signature, or memory — hits a dead page, and search engines can split signals or index the wrong host.
A request to https://technitask.com/ did not resolve to a working page; only https://www.technitask.com/ responded with a 200.
Add a permanent 301 redirect from the bare domain to your canonical host (or vice-versa) at the DNS / hosting level, so the domain always lands on the working site.
Every S&S build ships clean canonicals, a valid sitemap, robots.txt, and server-rendered HTML — indexability is table stakes, not an add-on.
What it costs you · Pages Google can't cleanly index don't show up — or show up as the wrong version.
None of the five pages includes a rel=canonical tag. Without a self-referencing canonical, Google must guess each page's canonical and can split or merge signals incorrectly — a real risk as soon as tracking parameters or www/non-www variants appear.
audit_page found canonical = none on all 5 audited URLs.
Add a self-referencing <link rel="canonical"> (the page's own clean URL) to every page's <head>.
Every S&S build ships clean canonicals, a valid sitemap, robots.txt, and server-rendered HTML — indexability is table stakes, not an add-on.
What it costs you · Weak titles and snippets cost you clicks even on pages that already rank.
Every page uses the same description ("Technitask provides IT management, applications, services, processes and people to the utility industry."). Google can't differentiate the snippets and will often replace them with weaker auto-generated text, hurting click-through on every page.
audit_page found an identical 104-character meta description on all 5 URLs.
Write a unique, page-specific 140–160 character description that states what each page offers and gives a reason to click.
We write 100% original titles, meta descriptions, and headings on every page — copywriting is bundled at every tier, where competitors charge $500–$3,000 a page.
What it costs you · Weak titles and snippets cost you clicks even on pages that already rank.
The five titles are "Technitask", "Contact", "Projects", "Services" and "Team" (4–10 characters). They omit the services offered and any brand/keyword pattern, so they rank for almost nothing and give a weak, ambiguous SERP listing that Google will often rewrite.
audit_page recorded title lengths of 4–10 characters across all 5 pages.
Write a unique 50–60 character title per page on a "{Primary keyword} | Technitask" pattern, e.g. "Utility-Industry IT Management & Services | Technitask".
We write 100% original titles, meta descriptions, and headings on every page — copywriting is bundled at every tier, where competitors charge $500–$3,000 a page.
What it costs you · Pages Google can't cleanly index don't show up — or show up as the wrong version.
The site has no robots.txt. Google treats this as 'allow all', so nothing is blocked, but you lose the standard place to point crawlers at your sitemap and to manage crawl of any future private paths.
check_robots received a 404 for /robots.txt.
Add a minimal robots.txt that allows crawling and includes a `Sitemap: https://www.technitask.com/sitemap.xml` line.
Every S&S build ships clean canonicals, a valid sitemap, robots.txt, and server-rendered HTML — indexability is table stakes, not an add-on.
What it costs you · Pages Google can't cleanly index don't show up — or show up as the wrong version.
The sitemap advertises all 5 URLs but none carry a <lastmod>, so Google has no freshness hint to prioritise re-crawling changed pages.
check_sitemap reported lastmod coverage of 0%.
Emit an accurate <lastmod> per URL from the CMS's true updated-at timestamp (don't fake it on every deploy).
Every S&S build ships clean canonicals, a valid sitemap, robots.txt, and server-rendered HTML — indexability is table stakes, not an add-on.
What it costs you · Weak titles and snippets cost you clicks even on pages that already rank.
Home, Projects, Services and About each render two H1s. Multiple H1s are not a ranking penalty, but a single descriptive H1 makes the page's primary topic unambiguous for users, Google, and AI extraction.
audit_page heading outlines showed h1_count = 2 on 4 pages (only /contact has one).
Keep one primary H1 per page (the main heading) and demote the secondary one to H2.
We write 100% original titles, meta descriptions, and headings on every page — copywriting is bundled at every tier, where competitors charge $500–$3,000 a page.
No schema and a JS-only contact page make the site hard for AI engines to read, understand, and cite.
We asked 6 AI engines "who is technitask.com?" — only 1 of 6 could name the business (Gemini). Only Gemini — Google's own — could confidently identify the business by name; the others returned no confident answer. Google knows who you are; the AI layer doesn't yet.
What it costs you · Pages Google can't cleanly index don't show up — or show up as the wrong version.
/contact ships a near-empty HTML shell and fills in client-side (~400 visible characters pre-render). Googlebot usually renders JS, but the first-pass index and — more importantly — AI crawlers and many tools see little content, risking missed indexing of contact details and weak AI citation.
audit_page's JS-dependency heuristic flagged /contact as js_dependent with ~399 visible characters in the raw HTML.
Server-render or statically pre-render the Contact page's core content (address, phone, form labels) so it is present in the initial HTML response.
Every S&S build ships clean canonicals, a valid sitemap, robots.txt, and server-rendered HTML — indexability is table stakes, not an add-on.
What it costs you · With no schema you forfeit rich results, and AI engines can't confidently cite you.
None of the pages include any JSON-LD or microdata. A utility-industry IT firm is missing Organization (name, logo, contactPoint → knowledge panel), WebSite (sitelinks search box), LocalBusiness, and BreadcrumbList markup — forfeiting rich-result eligibility and the entity clarity AI surfaces use to understand and cite a business.
validate_structured_data found zero JSON-LD blocks on all 5 URLs.
Add Organization + WebSite JSON-LD sitewide (logo, name, url, sameAs, contactPoint) and BreadcrumbList on inner pages; add LocalBusiness if there's a physical office.
Organization, FAQ, Person, LocalBusiness and Breadcrumb schema is baked into every build — for rich results today and machine-readable entity clarity for AI.
What it costs you · Slow, unstable pages lose visitors — and the AI citations that follow them.
No structured data (entity clarity), a JS-dependent Contact page, one-word titles, and thin content together make it hard for AI Overviews / AI Mode and assistants to understand and cite Technitask as the answer for utility-industry IT.
Synthesis across the audit: zero schema, /contact is JS-dependent, titles are 4–10 chars, and pages carry ~0.4–1.3k visible characters.
Add Organization/WebSite schema, server-render key content, write descriptive titles, and open key pages with a clear one-sentence answer to 'what does Technitask do for utilities?'.
AEO is baked in: llms.txt, an AI-bot allowlist, and entity + answer schema. We're our own case study — ~32% of our own traffic comes from AI engines.
Whether what they land on looks current, says something clear, and earns trust.
Service detail is locked in images, the copy is boilerplate, and 17 years of real expertise is never surfaced.
What it costs you · Thin pages can't demonstrate expertise, so they lose to deeper competitors.
Pages carry little substantive copy (Contact renders ~400 characters; the others ~1.1–1.3k). For competitive B2B "utility IT" terms there isn't enough depth to demonstrate expertise or rank against established competitors.
audit_page visible-text estimates ranged from ~399 (/contact) to ~1.3k characters.
Expand each page with specific, experience-led content — service detail, utility-sector case studies, named team expertise — not boilerplate.
We turn your existing assets into original, slop-gated pages — react, don't create — so depth and expertise show without you writing a word.
A clean but template-generic Webflow look that reads dated next to a modern competitor.
Clean but template-generic — a late-2010s Webflow build that reads dated to a 2026 buyer comparing you against a modern competitor. The strongest service detail is trapped inside images, so the page feels thinner than the business actually is.
Says 'SAP delivery partner,' but never states in five seconds who it's for or why you over a big-four firm.
The hero reads 'Your SAP Technical Delivery Partner,' but a first-time visitor can't tell in five seconds who it's for (utilities and the public sector) or why Technitask over a big-four consultancy.
A real team and named clients exist, but credentials, project outcomes, and proof aren't shown.
What it costs you · Thin pages can't demonstrate expertise, so they lose to deeper competitors.
Selling IT to utilities is a trust-heavy, high-stakes purchase, but the site shows little explicit authority signal (named experts, credentials, certifications, client/sector proof) that both buyers and Google's quality systems reward.
No author/credential or Organization/Person markup, and only light visible bios, were found across the audited pages.
Add a credible Team/About section with named experience and certifications, plus client/sector proof, and reinforce it with Person/Organization schema.
We turn your existing assets into original, slop-gated pages — react, don't create — so depth and expertise show without you writing a word.
Whether the site is fast, usable, and points to an obvious next step.
A contact form exists, but the JS-only contact page and weak CTAs lose ready buyers.
Assessed by expert review — no automated issues flagged here.
Mobile speed swings 56–83, there's no robots.txt, and no analytics baseline to measure from.
What it costs you · Slow, unstable pages lose visitors — and the AI citations that follow them.
Lab Lighthouse performance is 56 (Home) and 58 (About) on mobile — the slow band — with the rest 75–83. Slow loads hurt experience and conversion, and once the site gains traffic these will surface as Core Web Vitals problems.
psi.py mobile Lighthouse returned performance scores of 56 / 82 / 75 / 83 / 58 for home / contact / projects / services / about. No CrUX field data exists yet (low traffic), so this is lab-only.
Optimise the hero/LCP image, defer non-critical JS, and trim render-blocking CSS; re-measure once field data accrues.
Lighthouse 90+, sub-2s on 4G, and a mobile-first build come standard — speed is built in, not bolted on.
What it costs you · Slow, unstable pages lose visitors — and the AI citations that follow them.
PSI flags unused JavaScript/CSS and unminified CSS across the pages, each worth ~150–300 ms — low-effort wins toward LCP and INP.
psi.py lab opportunities listed 'Reduce unused JavaScript' (~150–300 ms), 'Reduce unused CSS', and 'Minify CSS' as top items.
Tree-shake and minify the bundle, purge unused CSS, and lazy-load non-critical scripts.
Lighthouse 90+, sub-2s on 4G, and a mobile-first build come standard — speed is built in, not bolted on.
The Search Console reports your findings map to — the problems Google surfaces only after months of lost traffic, where stale pages quietly drop out of the index. We flag them now, before you publish.
| Report | Predicted status | URLs | Severity |
|---|---|---|---|
| Core Web Vitals | Lab-only (no field data yet) | 2 | Important |
| Enhancements / Rich Results | No eligible items | 5 | Important |
| Page Indexing | Duplicate without user-selected canonical (risk) | 5 | Important |
| Page Indexing | — | 0 | Opportunity |
The 5 URLs we deep-audited, scored across all six facets. Search, sort, filter, and expand a row for the per-facet detail.
| URL | Crawl | Tech | Schema | Content | CWV | AI | |
|---|---|---|---|---|---|---|---|
/ Home· 200 | no canonical | 2×H1 | no schema | ok | lab 56 | review | |
/contact Contact· 200 | JS-dependent | title length | no schema | ok | lab 82 | JS-only | |
/projects Projects· 200 | no canonical | 2 issues | no schema | ok | lab 75 | review | |
/services Services· 200 | no canonical | 2 issues | no schema | ok | lab 83 | review | |
/about About· 200 | no canonical | 2 issues | no schema | ok | lab 58 | review |
The technical signals behind the findability scores — robots, sitemap, status codes, and per-page facets.
| Status | 404 |
|---|---|
| Sitemaps | none |
| Google-Extended | see note |
| URLs declared | 5 |
|---|---|
| lastmod coverage | 0% |
| Conflicts | 0 |
Titles, meta descriptions, headings, hreflang, alt text.
| / 2×H1 | 2×H1 |
| /contact title length | title length |
| /projects title length; 2×H1 | 2 issues |
| /services title length; 2×H1 | 2 issues |
| /about title length; 2×H1 | 2 issues |
Schema validity + rich-result eligibility.
| / No JSON-LD on the page | no schema |
| /contact No JSON-LD on the page | no schema |
| /projects No JSON-LD on the page | no schema |
| /services No JSON-LD on the page | no schema |
| /about No JSON-LD on the page | no schema |
Depth, trust signals, helpful-content alignment.
Clean — every audited URL passes this layer.
Verbatim output from each audit script — for provenance and reproducibility.
{
"target": "https://www.technitask.com/",
"robots_url": "https://www.technitask.com/robots.txt",
"status": 404,
"fetched": false,
"size_bytes": 2604,
"over_500kib": false,
"size_limit_bytes": 512000,
"groups": [],
"googlebot": {
"matched_user_agent": null,
"allow": [],
"disallow": [],
"crawl_delay": null,
"blocks_all": false,
"note": "no matching group and no '*' group => Google assumes allowed"
},
"google_extended": {
"matched_user_agent": null,
"allow": [],
"disallow": [],
"crawl_delay": null,
"blocks_all": false,
"note": "no matching group and no '*' group => Google assumes allowed"
},
"sitemaps": [],
"disallows_everything": false,
"notes": [
"robots.txt returned 404 (4xx). Google interprets an unavailable robots.txt as 'allow all', every URL becomes crawlable."
]
}{
"target": "https://www.technitask.com/",
"discovered_sitemaps": [
"https://www.technitask.com/sitemap.xml"
],
"sitemap_type": "urlset",
"url_count": 5,
"lastmod_present": false,
"lastmod_coverage": 0,
"sample_checked": [
{
"url": "https://www.technitask.com",
"status": 200,
"final_url": "https://www.technitask.com",
"meta_robots": null,
"canonical": null,
"reasons": [],
"conflict": false
},
{
"url": "https://www.technitask.com/contact",
"status": 200,
"final_url": "https://www.technitask.com/contact",
"meta_robots": null,
"canonical": null,
"reasons": [],
"conflict": false
},
{
"url": "https://www.technitask.com/projects",
"status": 200,
"final_url": "https://www.technitask.com/projects",
"meta_robots": null,
"canonical": null,
"reasons": [],
"conflict": false
},
{
"url": "https://www.technitask.com/services",
"status": 200,
"final_url": "https://www.technitask.com/services",
"meta_robots": null,
"canonical": null,
"reasons": [],
"conflict": false
},
{
"url": "https://www.technitask.com/about",
"status": 200,
"final_url": "https://www.technitask.com/about",
"meta_robots": null,
"canonical": null,
"reasons": [],
"conflict": false
}
],
"conflicts": [],
"notes": [
"No sitemap in robots.txt; trying /sitemap.xml."
]
}{}[
{
"target": "https://www.technitask.com/",
"final_url": "https://www.technitask.com/",
"status": 200,
"redirect_chain": [
{
"url": "https://www.technitask.com/",
"status": 200
}
],
"response_headers": {
"content-type": "text/html; charset=utf-8",
"content-encoding": "gzip",
"last-modified": "Tue, 19 May 2026 13:07:32 GMT",
"vary": "accept-encoding"
},
"html_bytes_raw": 21858,
"byte_limit_check": {
"html_bytes_raw": 21858,
"over_2mb_render_limit": false,
"limit_bytes": 2000000,
"context": {
"search_render_limit_bytes": 2000000,
"common_crawl_advisory_bytes": 15000000,
"absolute_cap_bytes": 64000000
}
},
"title": "Technitask",
"title_length": 10,
"meta_description": "Technitask provides IT management, applications, services, processes and people to the utility industry.",
"meta_description_length": 104,
"meta_robots": null,
"x_robots_tag": null,
"canonical": null,
"self_canonical": null,
"html_lang": "en",
"viewport": "width=device-width, initial-scale=1",
"viewport_present": true,
"hreflang": [],
"headings": {
"outline": [
{
"level": 1,
"text": "Your SAP Technical Delivery Partner."
},
{
"level": 2,
"text": "Our Services"
},
{
"level": 2,
"text": "We bring the technical know-how and implementation experience to augment your business and functional expertise."
},
{
"level": 2,
"text": "Our experience"
},
{
"level": 2,
"text": "We have a proven track record of successful technical delivery across utilities, the public sector and more."
},
{
"level": 2,
"text": "our team"
},
{
"level": 2,
"text": "We provide hands-on technical and functional expertise and advice to support your S/4 upgrades, cloud migrations, business transformations, and M&A initiatives."
},
{
"level": 2,
"text": "We are a team of on-shore, Canadian technical experts providing consulting, staff augmentation, and managed services, supported by our delivery frameworks, expert community, and lessons learned over 17 years of delivery across public and private sectors through various industries."
},
{
"level": 1,
"text": "Get in touch."
}
],
"counts": {
"h1": 2,
"h2": 7
},
"h1_count": 2,
"exactly_one_h1": false,
"flag": "Page should have exactly one H1; found 2."
},
"images": {
"total": 4,
"with_alt": 4,
"missing_alt": 0,
"sample_missing": []
},
"links": {
"internal": 15,
"external": 0,
"noncrawlable": 0,
"sample_noncrawlable": []
},
"structured_data": {
"json_ld_count": 0,
"json_ld_types": [],
"json_ld_summary": [],
"json_ld_objects": [],
"microdata_present": false,
"rdfa_present": false
},
"og_tags": {
"og:title": "Technitask",
"og:description": "Technitask provides IT management, applications, services, processes and people to the utility industry.",
"og:image": "https://cdn.prod.website-files.com/65b145664b05625abcd81b1e/65b2fd5913ceae9d943090db_technitask.png",
"og:type": "website"
},
"twitter_tags": {
"twitter:title": "Technitask",
"twitter:description": "Technitask provides IT management, applications, services, processes and people to the utility industry.",
"twitter:image": "https://cdn.prod.website-files.com/65b145664b05625abcd81b1e/65b2fd5913ceae9d943090db_technitask.png",
"twitter:card": "summary_large_image"
},
"js_dependent_heuristic": {
"js_dependent": false,
"visible_text_chars": 1166,
"spa_root_container": null,
"spa_root_empty": null,
"script_tag_count": 5,
"reasons": []
}
},
{
"target": "https://www.technitask.com/contact",
"final_url": "https://www.technitask.com/contact",
"status": 200,
"redirect_chain": [
{
"url": "https://www.technitask.com/contact",
"status": 200
}
],
"response_headers": {
"content-type": "text/html; charset=utf-8",
"content-encoding": "gzip",
"last-modified": "Sat, 30 May 2026 17:22:59 GMT",
"vary": "accept-encoding"
},
"html_bytes_raw": 12950,
"byte_limit_check": {
"html_bytes_raw": 12950,
"over_2mb_render_limit": false,
"limit_bytes": 2000000,
"context": {
"search_render_limit_bytes": 2000000,
"common_crawl_advisory_bytes": 15000000,
"absolute_cap_bytes": 64000000
}
},
"title": "Contact",
"title_length": 7,
"meta_description": "Technitask provides IT management, applications, services, processes and people to the utility industry.",
"meta_description_length": 104,
"meta_robots": null,
"x_robots_tag": null,
"canonical": null,
"self_canonical": null,
"html_lang": "en",
"viewport": "width=device-width, initial-scale=1",
"viewport_present": true,
"hreflang": [],
"headings": {
"outline": [
{
"level": 1,
"text": "Get in touch."
}
],
"counts": {
"h1": 1
},
"h1_count": 1,
"exactly_one_h1": true
},
"images": {
"total": 1,
"with_alt": 1,
"missing_alt": 0,
"sample_missing": []
},
"links": {
"internal": 10,
"external": 0,
"noncrawlable": 2,
"sample_noncrawlable": [
"mailto:contact@business.com?subject=You've%20got%20mail!",
"tel:6476601020"
]
},
"structured_data": {
"json_ld_count": 0,
"json_ld_types": [],
"json_ld_summary[
{
"target": "https://www.technitask.com/",
"final_url": "https://www.technitask.com/",
"psi_available": true,
"strategy": "mobile",
"field_data": null,
"origin_field_data": null,
"lab": {
"performance_score": 56,
"LCP": {
"display": "4.4 s",
"score": 0.4
},
"CLS": {
"display": "0.349",
"score": 0.32
},
"TBT": {
"display": "0 ms",
"score": 1
},
"FCP": {
"display": "4.2 s",
"score": 0.19
},
"SpeedIndex": {
"display": "5.1 s",
"score": 0.62
},
"TTI": {
"display": "4.4 s",
"score": 0.84
}
},
"opportunities": [
{
"id": "unused-javascript",
"title": "Reduce unused JavaScript",
"savings_ms": 150,
"display": "Est savings of 34 KiB"
},
{
"id": "unminified-css",
"title": "Minify CSS",
"savings_ms": 150,
"display": "Est savings of 3 KiB"
},
{
"id": "unminified-javascript",
"title": "Minify JavaScript",
"savings_ms": 150,
"display": "Est savings of 31 KiB"
},
{
"id": "unused-css-rules",
"title": "Reduce unused CSS",
"savings_ms": 150,
"display": "Est savings of 11 KiB"
}
],
"thresholds": {
"LCP": {
"good_max": 2500,
"poor_min": 4000,
"unit": "ms"
},
"INP": {
"good_max": 200,
"poor_min": 500,
"unit": "ms"
},
"CLS": {
"good_max": 0.1,
"poor_min": 0.25,
"unit": "score"
}
},
"notes": [
"No CrUX field data for this URL (common for low-traffic or new pages). Lab data only; field CWV will populate in Search Console once the URL gets enough real-user traffic."
]
},
{
"target": "https://www.technitask.com/contact",
"final_url": "https://www.technitask.com/contact",
"psi_available": true,
"strategy": "mobile",
"field_data": null,
"origin_field_data": null,
"lab": {
"performance_score": 82,
"LCP": {
"display": "4.2 s",
"score": 0.43
},
"CLS": {
"display": "0",
"score": 1
},
"TBT": {
"display": "0 ms",
"score": 1
},
"FCP": {
"display": "2.5 s",
"score": 0.66
},
"SpeedIndex": {
"display": "2.5 s",
"score": 0.97
},
"TTI": {
"display": "4.2 s",
"score": 0.85
}
},
"opportunities": [
{
"id": "unused-css-rules",
"title": "Reduce unused CSS",
"savings_ms": 150,
"display": "Est savings of 12 KiB"
},
{
"id": "unminified-javascript",
"title": "Minify JavaScript",
"savings_ms": 150,
"display": "Est savings of 31 KiB"
},
{
"id": "unused-javascript",
"title": "Reduce unused JavaScript",
"savings_ms": 150,
"display": "Est savings of 33 KiB"
}
],
"thresholds": {
"LCP": {
"good_max": 2500,
"poor_min": 4000,
"unit": "ms"
},
"INP": {
"good_max": 200,
"poor_min": 500,
"unit": "ms"
},
"CLS": {
"good_max": 0.1,
"poor_min": 0.25,
"unit": "score"
}
},
"notes": [
"No CrUX field data for this URL (common for low-traffic or new pages). Lab data only; field CWV will populate in Search Console once the URL gets enough real-user traffic."
]
},
{
"target": "https://www.technitask.com/projects",
"final_url": "https://www.technitask.com/projects",
"psi_available": true,
"strategy": "mobile",
"field_data": null,
"origin_field_data": null,
"lab": {
"performance_score": 75,
"LCP": {
"display": "4.3 s",
"score": 0.42
},
"CLS": {
"display": "0.023",
"score": 1
},
"TBT": {
"display": "230 ms",
"score": 0.87
},
"FCP": {
"display": "3.2 s",
"score": 0.44
},
"SpeedIndex": {
"display": "3.3 s",
"score": 0.91
},
"TTI": {
"display": "4.3 s",
"score": 0.84
}
},
"opportunities": [
{
"id": "unminified-css",
"title": "Minify CSS",
"savings_ms": 150,
"display": "Est savings of 3 KiB"
},
{
"id": "unminified-javascript",
"title": "Minify JavaScript",
"savings_ms": 150,
"display": "Est savings of 31 KiB"
},
{
"id": "unused-javascript",
"title": "Reduce unused JavaScript",
"savings_ms": 150,
"display": "Est savings of 34 KiB"
},
{
"id": "unused-css-rules",
"title": "Reduce unused CSS",
"savings_ms": 150,
"display": "Est savings of 12 KiB"
}
],
"thresholds": {
"LCP": {
"good_max": 2500,
"poor_min": 4000,
"unit": "ms"
},
"INP": {
"good_max": 200,
"poor_min": 500,
"unit": "ms"
},
"CLS": {
"good_max": 0.1,
"poor_min": 0.25,
"unit": "score"
}
},
"notes": [
"No CrUX field data for this URL (common for low-traffic or new pages). Lab data only; field CWV will populate in Search Console once the URL gets enough real-user traffic."
]
},
{
"target": "https://www.technitask.com/services",
"final_url": "https://www.technitask.com/services",
"psi_available": true,
"strategy": "mobile",
"field_data": null,
"origin_field_data": null,
"lab": {
"performance_score": 83,
"LCP": {
"display": "4.2 s",
"score": 0.44
},
"CLS": {
"display": "0",
"score": 1
},
"TBT": {
"display": "0 m[
{
"target": "https://www.technitask.com/",
"final_url": "https://www.technitask.com/",
"status": 200,
"blocks": [],
"summary": {
"json_ld_block_count": 0,
"types_found": [],
"has_required_errors": false,
"has_deprecated_types": false,
"note": "No JSON-LD structured data found. Microdata/RDFa, if any, are not validated here, run audit_page.py to detect their presence."
}
},
{
"target": "https://www.technitask.com/contact",
"final_url": "https://www.technitask.com/contact",
"status": 200,
"blocks": [],
"summary": {
"json_ld_block_count": 0,
"types_found": [],
"has_required_errors": false,
"has_deprecated_types": false,
"note": "No JSON-LD structured data found. Microdata/RDFa, if any, are not validated here, run audit_page.py to detect their presence."
}
},
{
"target": "https://www.technitask.com/projects",
"final_url": "https://www.technitask.com/projects",
"status": 200,
"blocks": [],
"summary": {
"json_ld_block_count": 0,
"types_found": [],
"has_required_errors": false,
"has_deprecated_types": false,
"note": "No JSON-LD structured data found. Microdata/RDFa, if any, are not validated here, run audit_page.py to detect their presence."
}
},
{
"target": "https://www.technitask.com/services",
"final_url": "https://www.technitask.com/services",
"status": 200,
"blocks": [],
"summary": {
"json_ld_block_count": 0,
"types_found": [],
"has_required_errors": false,
"has_deprecated_types": false,
"note": "No JSON-LD structured data found. Microdata/RDFa, if any, are not validated here, run audit_page.py to detect their presence."
}
},
{
"target": "https://www.technitask.com/about",
"final_url": "https://www.technitask.com/about",
"status": 200,
"blocks": [],
"summary": {
"json_ld_block_count": 0,
"types_found": [],
"has_required_errors": false,
"has_deprecated_types": false,
"note": "No JSON-LD structured data found. Microdata/RDFa, if any, are not validated here, run audit_page.py to detect their presence."
}
}
]How to read the report — and how it was run.
This is an agent-run, full-presence audit. The deterministic layer — search, schema, and performance — is generated by the open-source google-seo-auditor (one of six tools Space & Story built and runs in public): it fetches and parses the real page, maps every finding to one of 26 Google Search Console statuses across 5 families, and is benchmarked at 96% vs 66% with vs without the skill (eval iteration-2, May 2026). The judgment layer — design, message, content, and the "who is this business?" probe across six AI engines — is read by the agent. Deterministic where it can be; expert judgment where it counts.
Eight categories, grouped under three lenses — can they find you (Search, AI Search), will they believe you(Content, Design, Message, Trust), and will they act (Conversion, Performance) — each graded 0–100 and weighted into one composite. The → projected figures are where we'd take each score once the gaps are closed. Core Web Vitals follow Google's published p75 cutoffs, and we don't penalise myths — there's no duplicate-content penalty, E-E-A-T isn't a dial, and AI-assisted content isn't penalised for being AI-assisted.
Before the plan and the price: why Space & Story is the studio to close these gaps — with numbers from our own analytics, our own work, and our own open-source tools.
No other agency selling AEO shows this on their own analytics. The audit you're reading was generated by one of those six open-source tools — the google-seo-auditor.
Run by Mahmoud Halat.
This isn't a redesign — it's a system. Here's exactly how we turn Technitask's own expertise into a site that gets found, believed, and cited — you react, we don't make you create.
Everything you've already got — case studies, project write-ups, RFP responses, decks, talks, audio and video. Most of it is gold that's currently trapped in PDFs and images, invisible to Google and AI.
We read all of it and pull out what matters: the topics your buyers actually search, the projects that map to that demand, and the language that already wins you work. You never face a blank page — we react to what you have, we don't invent.
Your expertise becomes a structured, AI-readable site — programmatic pages built from your own data (up to 200 on the Engine build), 100% original copy, every word through our anti-slop audit. Real depth, not filler.
On a private staging site you leave voice or text feedback while it records the session; that becomes an auto-built task list we work through. No standing meetings, no homework.
Hosting and AEO go live, with a dashboard that splits your traffic into Human / SEO / AI so you can watch it land — live in 30 days.
We track what's getting found and which pages AI is pulling from, double down on the themes that perform, and keep shipping — with a monthly strategist call to steer it.
Your tailored build + monthly plan, the full price, and how to move forward are private — sign in with your approved email, or request access.