Match the buyer’s problem.
State the service, the audience and a useful next step. For digitisation, explain the records problem and scoping conversation rather than leading with generic technology language.
Website build and SEO
A stronger website.
Every page earns its place.
A page-by-page build plan based on Integra’s current site and the public approaches of twelve relevant providers.
Keep the expertise. Make the route to an enquiry clearer.
Integra already has substantial service knowledge, energy-sector experience and four customer stories. The build will organise those assets into clearer service destinations, useful proof and a trackable next step. It will connect the website to the Ruddr sales workflow and Power BI reporting described in this proposal.
15Proposed core pages
4Existing stories to preserve
4Connected form types
12Provider websites reviewed
This expands the explanation of the agreed website scope; it does not add fees or unlimited pages. Final URLs and content are approved with Integra before build. Existing story/article migration remains within the allowance of up to 20 approved entries.
What the current-site review found.
Reviewed 10 November 2026: the ten URLs in Integra’s public XML sitemap, the root homepage and a linked utility route. Browser checks covered the homepage, contact page, solutions page and asset-information route. The review examined public content, headings, metadata, links and rendered forms; it did not submit forms or access private analytics.
| Observed evidence | What it means for the build | Source |
|---|---|---|
| The sitemap lists ten URLs, including four detailed customer stories. | Preserve those assets and establish a URL/content inventory before design. | S02 S41 |
| Homepage service summaries lead to the same combined /solutions destination. | Add focused service pages that can answer a specific buyer question and match the campaign. | S01 S38 |
| Five homepage discovery CTAs open an email application. The contact page has a browser-rendered name/email/message form. | Keep contact options, while making a saved, service-prefilled form the principal measurable enquiry path. | S01 S39 |
| /asset-information-management-1 returns HTTP 200 and is sitemap-listed, but had no substantive main content or visible headings in the browser review. | Create the substantive asset-information destination and approve the old-to-new route mapping. | S40 S41 |
| /solutions has an H2 but no H1 in the reviewed output; some stories use H1s for results/statistics. | Use a consistent semantic hierarchy with one clear page topic and properly nested sections. | S38 S02 |
| The contact page title contains a spelling error; the thin asset route lacks a description. | Review page-specific titles/descriptions rather than remove metadata that already exists. | S39 S40 |
| The root and /home both load; /home already declares the root as canonical. Robots.txt and XML sitemap are present. | Preserve and validate the canonical policy and crawl controls through migration. | S01 S41 S42 |
| Existing structured data and business contact information are present. Some images have empty or absent alt text. | Validate the existing markup and distinguish informative images from decorative assets before writing alt text. | S01 S38 |
The contact form renders after JavaScript loads. It was confirmed in the browser even though it was not present in the initial HTML response. Existing form delivery, analytics events and any Ruddr connection require account-level verification.
A simple navigation built around the buyer.
ServicesGovernance, Microsoft 365, Copilot readiness, digitisation, asset information and managed services
IndustriesEnergy and engineering context, linked to relevant service pages and approved customer stories
Proof and insightCustomer stories, practical articles, resources and confirmed webinars
Talk to IntegraOne clear consultation or project enquiry, with service interest carried into the form
Keep the primary navigation short: Services, Industries, Customer Stories, Insights, About and Contact. Resources can sit under Insights; privacy and utility links belong in the footer. A discovery CTA stays easy to reach on mobile.
The 15 core pages: what we are adding and why.
Five existing core destinations are retained and improved. Ten dedicated destinations are proposed from the services and buyer journeys identified in the review; their final existence, naming and URL are confirmed against the full CMS inventory. A page is not added merely to repeat a keyword.
01 · Home
Retain and improve
Proposed URL: /
Who it helps: Executives, IT and operations leaders arriving from search, referrals or campaigns.
Why this page: Make the range of services understandable quickly and route visitors to the right service.
What we add: A concise positioning statement, service routes, energy/engineering proof, selected stories and a prominent consultation CTA.
Search and internal linking: Retain the preferred root URL; write a clear brand/service title and a logical H1/H2 hierarchy.
Primary next step: Choose a service or request a discovery call.
02 · About and team
Retain and improve
Proposed URL: /about-us
Who it helps: Buyers checking credibility and the people behind the work.
Why this page: Help a prospective client assess fit and delivery experience.
What we add: Approved team profiles, relevant credentials, approach and sector experience; retain useful careers information as a section.
Search and internal linking: Keep the established URL and connect consultants to the relevant services and approved stories.
Primary next step: Meet the team and discuss a relevant project.
03 · Solutions overview
Retain and improve
Proposed URL: /solutions
Who it helps: Visitors who recognise a business problem but need help choosing the service.
Why this page: Turn a long combined service page into a useful decision hub.
What we add: Brief service summaries, problem-led navigation and links to the six dedicated service destinations.
Search and internal linking: Keep the existing URL; use a descriptive primary heading and contextual links rather than duplicating full service copy.
Primary next step: Select a service or request help choosing the first step.
04 · Information governance and records strategy
Proposed dedicated destination
Proposed URL: /services/information-governance
Who it helps: CIOs, records leaders and business owners with ownership, retention or findability problems.
Why this page: Give the existing governance offer its own useful destination for search, LinkedIn and sales follow-up.
What we add: Assessment scope, governance/roadmap deliverables, roles, adoption process, relevant proof and FAQs.
Search and internal linking: Candidate focus: information governance consulting and records-management advisory; link from the solutions hub and practical articles.
Primary next step: Request an information health or governance discussion.
05 · Microsoft 365 and SharePoint
Proposed dedicated destination
Proposed URL: /services/microsoft-365-sharepoint
Who it helps: IT owners planning migration, permissions, collaboration or workflow improvements.
Why this page: Explain the technology-services offer in the terms a buyer is searching for.
What we add: Architecture/governance, migration preparation, metadata, permissions, adoption and relevant workflow examples.
Search and internal linking: Give migration, governance and workflow sections distinct headings; link to the Modern Workspace story and related articles.
Primary next step: Discuss a Microsoft 365 or SharePoint project.
06 · Copilot and AI information readiness
Proposed dedicated destination
Proposed URL: /services/copilot-readiness
Who it helps: IT and governance sponsors preparing an AI initiative.
Why this page: Connect the current AI-readiness positioning to a clearly scoped first engagement.
What we add: Information ownership, permissions/content review, a representative pilot and the deliverables Integra agrees to provide.
Search and internal linking: Candidate focus: Copilot information readiness; avoid claiming unsupported product capabilities or guaranteed outcomes.
Primary next step: Discuss a scoped readiness review, subject to Integra’s approved offer.
07 · Document digitisation and scanning
Proposed dedicated destination
Proposed URL: /services/document-digitisation
Who it helps: Records and operations owners with paper backlogs or retrieval problems.
Why this page: Provide a focused destination for the initial scanning searches and project enquiries.
What we add: Formats and scope, preparation, OCR/indexing, quality controls, access, delivery destination and an approved relevant story.
Search and internal linking: Candidate focus: document scanning Calgary and digitisation services. Explain real service coverage rather than creating repetitive city pages.
Primary next step: Submit a digitisation project brief.
08 · Asset information and engineering handover
Replace thin route
Proposed URL: /services/asset-information-management
Who it helps: Engineering, project information and operations teams.
Why this page: Replace the sitemap-listed empty-content destination with a substantive buyer journey.
What we add: Drawings and operational records, metadata/revision control, handover acceptance, responsibilities and existing project stories.
Search and internal linking: Map /asset-information-management-1 to the approved substantive destination if the URL changes.
Primary next step: Discuss a handover or asset-information review.
09 · Managed information services
Proposed dedicated destination
Proposed URL: /services/managed-information-services
Who it helps: Leaders seeking ongoing support beyond a one-off project.
Why this page: Make the existing managed-service offer easier to evaluate.
What we add: Support scope, ownership, governance reviews, reporting rhythm and a practical transition into recurring service.
Search and internal linking: Differentiate recurring support from project services and link to governance, M365 and relevant proof.
Primary next step: Discuss recurring information support and priorities.
10 · Energy and engineering industries
Proposed dedicated destination
Proposed URL: /industries/energy-engineering
Who it helps: Energy, mining, utilities and engineering decision-makers assessing sector fit.
Why this page: Bring existing sector experience and stories into a coherent industry context.
What we add: Relevant record types, operational scenarios, service routes and approved sector-specific proof.
Search and internal linking: Use substantive sector context and actual service geography; avoid unsupported claims about every industry or location.
Primary next step: Choose the relevant service or discuss an operational information problem.
11 · Customer stories hub
Retain and improve
Proposed URL: /customer-stories
Who it helps: Buyers validating approach and delivery relevance.
Why this page: Make the four current stories easier to discover from the right service.
What we add: Organise existing stories by problem, sector and service, with clear summaries and useful related links.
Search and internal linking: Retain existing story URLs where practical and link from service pages to relevant proof.
Primary next step: Read a relevant story, then discuss a similar challenge.
12 · Insights and practical articles
Proposed content hub
Proposed URL: /insights
Who it helps: Researchers and prospective buyers learning about a specific information problem.
Why this page: Provide a useful home for the two monthly articles in the managed programme.
What we add: Editorial categories, article pages, reviewer/author context, related services and relevant resource CTAs.
Search and internal linking: Map each article to a distinct question; link articles to service pages and avoid competing articles targeting the same intent.
Primary next step: Read the next practical step or request a service discussion.
13 · Resources and webinars
Proposed content hub
Proposed URL: /resources
Who it helps: Interested prospects who need a checklist, worksheet or confirmed educational session.
Why this page: Make the planned resources useful conversion paths rather than isolated attachments.
What we add: Quarterly resources, clear preview/value descriptions, confirmed webinar details and separate subscription choices.
Search and internal linking: Create useful summaries with original context. Treat a download or registration as an engagement, not an automatically qualified lead.
Primary next step: Request a resource or register for a confirmed webinar.
14 · Contact and project enquiry
Retain and improve
Proposed URL: /contact-us
Who it helps: Visitors ready to speak to Integra or describe a project.
Why this page: Keep the existing contact destination and add clearer business context and routing.
What we add: Service-prefilled enquiry/project forms, existing contact details, optional phone and an expectation of the next step.
Search and internal linking: Correct the title copy, retain the established URL, and track successful saved submissions separately from button clicks.
Primary next step: Submit a relevant enquiry; phone and email remain alternatives.
15 · Privacy and website information
Proposed policy destination
Proposed URL: /privacy
Who it helps: Visitors checking how form and website information is used.
Why this page: Make the approved privacy information easy to find beside data collection.
What we add: Publish Integra-approved notices, contact details and relevant preference/cookie information. Confirm whether an existing policy URL should be retained.
Search and internal linking: Keep policy links consistent; indexing and consent settings follow the approved implementation.
Primary next step: Understand the information use and manage relevant choices.
Counting the scope: these 15 are core pages. The four existing case stories are retained or migrated as content entries within the separate allowance of up to 20 approved articles/stories. Forms are embedded in the relevant pages; they do not create four extra core pages. Confirmation and 404 states are utility layouts. Additional standalone service or sector pages replace a page in this plan or require a separately agreed change.
Preserve the customer stories that already do the selling.
The existing stories provide context for Microsoft 365, engineering records, digitisation and handover. Keep their established URLs where practical, use approved figures with their original context, and place a relevant story beside each service enquiry CTA.
| Existing content | Keep / reuse decision | Where it supports the journey |
|---|---|---|
| Embracing a Modern Workspace | Retain /embracing-a-modern-workspace and refresh the presentation. | Microsoft 365, governance and energy page proof. |
| Engineering a Better Future | Retain /engineering-a-better-future and link from asset information. | Engineering/operations audiences assessing a handover or control problem. |
| Enabling AI Through Imaging Critical Operational Records | Retain the existing story URL and review the heading structure. | Digitisation and AI-readiness preparation. |
| No Data Left Behind | Retain /no-data-left-behind and explain the business problem, approach and outcome clearly. | Asset-information transition and energy-sector proof. |
What the competitor scan tells us to build.
These are public-page observations and recommended responses, not conclusions about search rankings, market share or conversion performance. The six direct providers and six adjacent/regional alternatives were reviewed as the defined comparison set. Iron Mountain’s direct HTML fetch was rate-limited; its public page was reviewed through web retrieval.
| Provider | Observed website approach | What we take into Integra’s build | Evidence |
|---|---|---|---|
| Gravity Union | Separate service/technology routes, case stories and a governance page with a specialist CTA. | Give each priority service a focused explanation and link it to relevant proof. | S03 S43 |
| WCD | A dedicated scanning destination, related conversion services and an expert-contact route. | Explain scope, output quality and the consultation, not just the scanning equipment. | S07 S44 |
| Tesseract Solutions | A services page covering IM, BI and web development with a contact next step. | Keep the service choice explicit and show Integra’s own delivery approach. | S09 |
| Access Calgary | A Calgary-specific location/service page with local details and scanning/lifecycle information. | Use genuine Calgary business details and explain actual coverage; avoid thin location duplication. | S10 |
| Ricoh Canada | A dedicated governance-consulting page with an assessment-to-roadmap sequence. | Make the first engagement and its practical deliverables easy to assess. | S11 |
| Johal Consulting | Named records health-check and digitisation advisory offers. | Package a useful entry conversation with clear preparation and next steps. | S12 |
| Copyseis | Records/storage service categories and explicit energy-industry context. | Create substantive industry context and connect it to approved energy/engineering proof. | S13 |
| Iron Mountain Canada | A digitisation page with process, capabilities and FAQs. | Answer practical scoping questions and distinguish Integra’s approved service approach. | S14 |
| Cadence Solutions | Named readiness, governance and health-check destinations; articles and webinars. | Create a focused AI-readiness destination and a coherent resource path. | S15 S45 |
| Long View Systems | Organised solution families with case-study and contact routes. | Keep navigation understandable and help buyers reach the relevant specialist service. | S16 |
| ARC Calgary | A local branch destination with service navigation and multiple enquiry routes. | Make service selection and the appropriate enquiry route clear on mobile. | S17 |
| DHQ Imaging Centre | A scanning/OCR service page with format explanations and a quote CTA. | Describe real formats, outputs and the scope information a buyer should provide. | S18 |
SEO changes that support the page plan.
The work starts with crawlable, useful service content and preservation of existing assets. Search visibility is measured after launch; rankings and lead volumes are not guaranteed. Titles, descriptions and headings are written for the page’s audience, rather than repeated across the site.
| Workstream | Specific change | How we check it |
|---|---|---|
| Page architecture and search intent | Create the approved dedicated service pages and a useful solutions hub; map one principal buyer intent to each. | A page/keyword/CTA map approved before writing; no unsupported volume or ranking claims. |
| Titles and descriptions | Write unique service-led titles, fix the contact-title typo and fill appropriate missing descriptions. | Review every approved indexable page for uniqueness, accuracy and readable search snippets. |
| Headings and useful copy | Use a clear page topic, nested section headings, practical service scope, FAQs and approved proof. | Check rendered headings and copy on desktop/mobile; avoid decorative statistics as primary headings. |
| Internal links and proof | Connect the solutions hub, service pages, relevant stories, articles and resources. | Every priority service has a clear path from navigation and relevant contextual links. |
| Local relevance | Use the real Calgary address/contact details and genuine coverage; review the existing Google Business Profile with access. | Consistent business details and substantive local relevance; no fabricated offices or mass city pages. |
| Structured data | Validate existing organisation/site markup, and add appropriate supported article, breadcrumb or business details where applicable. | Match markup to visible content; validate it without promising special search features. |
| Performance and accessibility | Measure representative mobile/desktop pages; optimise measured image, layout and interaction issues; provide suitable alt text and keyboard labels. | A recorded baseline and launch review. No performance score or Core Web Vitals result was measured in this scan. |
| Indexing and migration | Approve canonicals, one-hop redirects, crawl rules and an indexable production sitemap; keep utility/staging routes appropriate. | Inspect the redirect map and Search Console coverage once access is granted. |
| Measurement and ongoing improvement | Define valid enquiry completion, campaign source and service-interest events; review queries/pages alongside sales outcomes. | Distinguish saved enquiries from clicks, downloads, spam and overlapping platform conversions. |
Existing metadata, canonical tags, HTTPS, structured data and the robots/sitemap setup are part of the baseline to preserve and validate. This review does not claim they are all missing. Heading cleanup improves document structure and accessibility; it is not presented as an automatic ranking gain.
How a service page is built to earn the enquiry.
Answer the questions that delay a call.
Show formats, preparation, indexing/OCR, quality checks, access and the agreed delivery destination where relevant. Place an approved story or sample deliverable beside that explanation.
Keep one principal next step.
Use a service-prefilled consultation or project brief. Retain phone and email as alternatives. Resource downloads are secondary actions, with newsletter consent kept separate.
Connect the request to sales.
Save a submission ID and permitted source fields, route the request to an owner and record its outcome. Report completed valid requests separately from CTA clicks and rejected spam.
Four forms, designed around the request.
The current contact form is a useful starting point. The proposed forms add business context and a dependable downstream handoff without asking every visitor to complete the same long questionnaire.
| Form type | Fields and purpose | Where it appears |
|---|---|---|
| Consultation | Name, business email, company, service interest and a short need. Phone optional. | Service pages and Contact; prefill the originating service. |
| Project brief | The consultation details plus relevant scope questions: record types, approximate volume, current systems or timing as appropriate. | Digitisation, asset information and campaign pages; request only information sales will use. |
| Resource / webinar | Minimum details required for the resource or event, with marketing consent separate. | Resource pages and confirmed event pages. |
| Newsletter signup | Email, optional name and a clear subscription choice. | Insights, article footer and Resources. |
All forms require validation, spam handling, saved submissions, visible delivery exceptions and an assigned follow-up route. Confidential document upload, bespoke booking software and extra CRM products are not implied by this scope.
Migration without discarding what already works.
Approve the inventory and redirect map before the rebuild replaces the current site. The final route decisions use the CMS inventory and Search Console/analytics data supplied during onboarding; public inspection alone cannot identify every valuable incoming link.
| Current route / asset | Proposed treatment | Acceptance check |
|---|---|---|
| / and /home | Keep one preferred homepage. The existing /home canonical points to the root; retain a consistent canonical/redirect policy. | One indexable preferred home, consistent links and no redirect chain. |
| /solutions, /about-us, /contact-us, /customer-stories | Keep the established URLs while improving content and layout. | Existing links resolve and each page has a suitable title, heading and next step. |
| /asset-information-management-1 | Replace the empty-content destination with the approved substantive asset page; redirect the old path if its URL changes. | Relevant one-hop redirect, content visible and sitemap updated. |
| Four existing story URLs | Retain where practical; preserve approved copy/results and link to matching services. | Stories load, images/captions work and links from service pages are tested. |
| New services, Insights and Resources | Add only approved core routes, related content and useful internal links. | No placeholders, duplicate titles or accidental staging noindex on production. |
| Cart and other utility routes | Confirm whether commerce is needed. Remove unnecessary navigation and handle indexing appropriately. | Useful 404/utility behaviour without redirecting unrelated URLs to the homepage. |
What is built once and what improves each month.
The setup creates the architecture, templates, connected forms, initial approved content and launch foundations. The managed service then maintains the publishing and review process within its stated allowances.
| During implementation | Through the monthly service | Requires separate agreement |
|---|---|---|
| Core page structure, approved copy/layout, metadata, redirect map and form handoff. | Two articles, two emails, scheduled social, priority-page review and search-query/indexing checks. | Core pages beyond 15 or migration beyond the agreed content allowance. |
| Baseline measurements, consent-aware events, six report pages and source definitions. | Minor website/content improvements up to two hours and minor report adjustments up to one hour monthly. | Major redesigns, additional custom templates or new integration systems. |
| Approved launch checks, training and operating guide. | Campaign changes informed by real enquiries, content performance and sales outcomes. | Unscoped historical data reconstruction or guaranteed ranking/lead commitments. |
Confirm the final sitemap, priority offers, proof assets, content owners and approval dates at kickoff. This page plan sits inside the agreed CAD $13,505.90 implementation and CAD $4,362.47 monthly service proposal; advertising remains CAD $2,000 monthly separately.
Website acceptance checklist.
Content and service clarity
Every approved core page has its intended audience, purpose, usable content and next step. Client claims, credentials and customer results are approved.
Search foundations
Validate titles, descriptions, visible headings, canonical routes, robots rules, XML sitemap, internal links and appropriate structured data. Preview crawl restrictions must not leak onto the real client website.
Enquiries and source tracking
Test every active form for success, invalid fields, duplicates and delivery failure. Confirm owner routing, consent records and source fields, using labelled test requests.
Mobile, access and performance
Review representative layouts, keyboard navigation, labels, focus states and images. Establish a measured performance baseline and address material build issues; this review does not assign a Lighthouse/Core Web Vitals score.
Migration and launch
Check the URL map and priority redirects, retain the existing site through rollback preparation, verify production indexing intent and provide editor/owner training.
Post-launch review
Check Search Console coverage and crawl errors, inspect real enquiry delivery and review page/campaign outcomes. Prioritise improvements from observed data.