Server Care preview
Build notes
What was checked, where every sentence came from, and what it would take to run this page on your own site.
Tested in this preview
Run on 17 September 2026 at 13:31 UTC against the live page at https://foruminfotech-pages.theaipipe.com/. Every line below is the output of a tool, not a claim, and each one links to what that tool wrote.
Structured data, validated
validator.schema.org, which fetched the page itself
No errors, 0 warnings
Types parsed: WebPage, Service, LocalBusiness, PostalAddress, Country, AdministrativeArea, FAQPage, Question, Answer.
Open the tool outputContent and markup agree
scripts/parity-check.mjs, run against the served HTML
32 statements checked, all readable on the page
Every sentence the structured data asserts has to appear in the body of the same page. Valid markup that says something the page does not say is the failure this catches.
Open the tool outputEvery sentence traced back to your site
scripts/source-check.mjs, which fetches each source page again
23 passages found on the pages they came from
Includes the pairing check on all 7 question and answer pairs: each answer sits under the question that heads its own page.
Open the tool outputField mapping, checked against expected results
node --test, against six cases written in a separate file
20 tests green
A complete submission, an empty optional field, a missing required field, a malformed address, a field the mapping does not declare, and two fields landing on the same property.
Open the tool outputThe tests fail when the mapping is wrong
scripts/mutation-check.mjs, which breaks the mapping on purpose
4 deliberate changes, every one caught
A green suite proves nothing on its own. A property is renamed, two fields are pointed at the same property, a required flag is dropped, a proposal is passed off as a standard property. Each has to turn the suite red, and the file is restored afterwards.
Open the tool outputThe form on this page, driven in a browser
Playwright, starting from the fields the page renders
8 checks passed
Typing, submitting, refusing an incomplete submission, capturing the request on the wire and reading the property names out of it, and a request that never arrives being reported rather than passed off as a success.
Open the tool outputNothing reaches HubSpot, or you
Playwright, recording every request the page makes
No delivery, and none attempted
21 requests were made while the form was filled in and submitted, and every request stayed on this origin. No portal identifier exists in this project to send one with.
Open the tool outputLighthouse, mobile, 5 runs
Lighthouse 13.4.1, headless, on this URL
Performance 98 to 99, accessibility 100, best practices 100, SEO 63
Performance, accessibility, best practices and SEO, for each run in turn. run 1: 98 / 100 / 100 / 63; run 2: 99 / 100 / 100 / 63; run 3: 98 / 100 / 100 / 63; run 4: 98 / 100 / 100 / 63; run 5: 98 / 100 / 100 / 63. Every run is reported, not the best of them. The SEO score is held down by one audit, is-crawlable, and that is correct: this page tells crawlers not to index it, which is the right setting for a preview that is not yours yet. It stays, and the score stays with it.
Open the tool outputThe page checked and the page you can open are the same page: 86c0a997c8a8 for its 531 words, and 07a52b9e716b for its structured data. sha256 of the page's visible text, and of its structured data, first twelve characters. Run node scripts/fingerprint.mjs https://foruminfotech-pages.theaipipe.com/ and the two either match or they do not.
What that adds up to: the content is in the HTML, the markup is valid, and the two agree with each other. None of it is a measurement of visibility. A page marked noindex cannot be one, and no markup makes an answer engine quote anybody.
Sources and assumptions
Every sentence on the page is yours, read from a public page on 17 September 2026 and kept in the scope it was written for.
The sentence that defines Server Care, used as the opening answer.
The two descriptions of Server Care, one written for servers on site and one for servers in the cloud. No figure from that page is reproduced anywhere.
Question and answer as published, each pair taken from a single page and read before use.
Postal address, telephone and the areas you list. Published email addresses were left out on purpose.
Rubik and Poppins, your palette, your logo, and the social profiles you already declare, reused rather than reconstructed.
Choices we made, and why
The two service descriptions are shown side by side, not merged.
One was written for servers you run on site, the other for servers in the cloud. Merging them would quietly widen what Server Care promises.
Seven questions out of your thirty-eight.
The ones someone weighing up who should look after their servers actually asks. Each answer is yours, unedited.
The credential figures come from your FAQ entry published on 8 August 2026.
It is the most recent of the pages that carry them.
Two colours are a shade darker here than on your site.
Your link blue and your lightest grey fall just under the contrast a small line of text needs to stay readable. Headings, rules and buttons keep your colours exactly as you publish them; small text uses a darker shade of the same two.
No client quotation, no photograph, no award mark.
Reproducing a client's words on a page they have not seen is a borrowing we are not entitled to make.
Open, and yours to settle
Does Server Care include backups, or does Data Care?
Your managed IT services page says Server Care includes backups. Your calculator names Data Care separately for backups, and describes Server Care without them. The preview quotes each sentence in its own scope and settles nothing. Whichever answer is right, it is worth being the same on both pages, because a machine reading your site cannot tell which one you meant.
Three of your pages give different figures for the same facts.
Devices under management, networks under management and your rank on the MSP 501 list appear with different values depending on the page. The preview uses the most recent set. Picking one and repeating it everywhere is worth more than any markup.
Where should a Server Care lead land?
Creating a contact and creating or routing a deal are two different operations. Contact only, lead status, owner, deal and stage, internal notification: that is a decision about how your team works, not a technical one, and it is the first thing to settle before anything is connected.
Three of the fields are suggestions, not facts about your CRM.
First name, last name, email, company and phone are properties every HubSpot portal already has. Number of servers, the campaign fields and the message field are proposals. They have to exist in your portal, under names your team chooses, before a form can fill them.
Publishing on your existing site
This preview is a draft to look at, not an architecture to adopt. The page is plain HTML with one demonstration endpoint behind the form; it is built the way it is so it could be checked, and your site can carry the same structure however it is built today.
Needed
Give the page its real address on your own domain
Today it sits on our subdomain and tells search engines not to index it. Moving it to your site is the whole point, and that is where the canonical link and the indexing decision belong.
Needed
Decide what the form has to do before connecting it
The target form, the properties it writes to, which fields are required and what happens after a submission. Connecting before that settles is how a CRM fills up with properties nobody chose.
Needed
Run it against a HubSpot test portal, with your permission
The checks here stop at the request. Watching a real portal accept it, and a contact appear where you expect, is the next level of proof and it takes an account you control.
To confirm
Check the spam setting on the target form
HubSpot does not accept submissions through the Forms API when CAPTCHA is turned on for that form. Their native embed avoids the question entirely and is often the simpler thing to maintain. Worth deciding on purpose rather than discovering later.
Optional
Link the page from where your visitors already are
Your managed IT services page names Server Care and has nowhere to send a reader who wants more. That link is worth more than any markup on the page.
Optional
Reuse the same shape for the other services
The structure here holds for anything you name and describe. Nothing about it is specific to servers.
Any of this worth talking through? Fifteen minutes is enough.
https://cal.theaipipe.comFrederic de Lavenne de Choulot, The AI Pipe. Back to the page.