Your project, at a glance.
A clear view of what’s delivered and what comes next.
Approximately four-fifths of the project effort delivered.
Weighted by estimated effort across 37 tracked tasks.
This percentage includes work completed on the staging website. It does not mean 80% of the changes are live, or measure search rankings, traffic or enquiries.
Progress by workstream
Based on the same effort weights
Strategy & foundations
100%
Audit, content strategy and measurement foundations.
Website & navigation
90%
Page design, product discovery and navigation.
Content & search readiness
76%
Search signals, solution pages and business information.
Reliability & release
23%
Hosting checks, release preparation and launch.
Solid foundations. Better experience.
- Strategy and measurement establishedTechnical audit, content architecture, search baseline and reporting framework completed.
- Navigation and page design improvedCatalogue navigation, footer, product layouts and equipment subpage styling completed on staging.
- Content connections strengthenedInternal links, equipment navigation and substantial technical SEO repairs completed.
- Latest catalogue refinements finishedSPY portable and in-plant catalogues corrected and styled consistently.
The path to release.
- Finish content and search improvementsFour category pages, structured data, solution-page review and Bing setup.
- Complete checks and final acceptanceContact email delivery, PDF-icon review and hosting reliability checks.
- Reconcile and prepare the releaseRemaining PDF originals, redirects, SEO changes and the coordinated production package.
- Approve, launch and verifyAgree release scope and timing, take backups, deploy and check the live website.
The work behind the number
37 tasks · 228 effort points
Larger tasks carry more weight. Expand a task to see its estimate notes. “Complete” refers to that task’s scope, often delivery on staging.
Showing all 37 tasks
| Ticket | Task / estimate notes | Points | Completion |
|---|---|---|---|
| #1 on GitHub |
Complete live-site technical & AEO baseline auditTechnical baseline audit across several disciplines. GitHub issue: closed. |
5 | Complete |
| #2 on GitHub |
Resolve DNS and complete staging environment setupDNS, isolated staging, SSL and environment QA. GitHub issue: closed. |
5 | Complete |
| #3 on GitHub |
Define Tremco Pipeline Equipment entity, authority and trust signalsBusiness/entity fact framework and authority planning. GitHub issue: closed. |
3 | Complete |
| #4 on GitHub |
Redesign homepage content structure for AEO and SEOHomepage structure, copy and metadata. GitHub issue: closed. |
5 | Complete |
| #5 on GitHub |
Design solution-led site architecture and landing pagesSolution architecture, URL mapping and content briefs. GitHub issue: closed. |
5 | Complete |
| #6 on GitHub |
Create AEO product-page content template and optimise priority pagesReusable product template and priority drafts; later implementation counted separately. GitHub issue: closed. |
5 | Complete |
| #7 on GitHub |
Build technical knowledge centre and answer-engine content planKnowledge-centre research, backlog and briefs. GitHub issue: closed. |
5 | Complete |
| #8 on GitHub |
Audit and implement structured data strategyComplex schema implementation and validation; 60% explicitly recorded in latest updates. GitHub issue: open. 60% completion is recorded in the ticket. |
13 | 60% |
| #9 on GitHub |
Improve internal linking and semantic site relationshipsBroad internal-link implementation and crawl QA; excludes follow-up PDF restoration in #28. GitHub issue: closed. |
13 | Complete |
| #10 on GitHub |
Establish AI-search and organic visibility baselineRepeatable organic and AI visibility baseline. GitHub issue: closed. |
5 | Complete |
| #11 on GitHub |
Set up Bing Webmaster Tools and search-engine monitoringBing verification, sitemap submission and baseline still pending. GitHub issue: open. |
3 | Pending |
| #12 on GitHub |
Complete competitor and content-gap analysisCompetitor research and content gap analysis. GitHub issue: closed. |
5 | Complete |
| #13 on GitHub |
Define AEO/SEO measurement and client reporting frameworkMeasurement and reporting framework. GitHub issue: closed. |
3 | Complete |
| #14 on GitHub |
Obtain and audit Google Business Profile accessAccess and initial baseline established; ownership and factual reconciliation outstanding. Completion estimated. GitHub issue: open. Partial completion is estimated from recorded work. |
5 | 40% |
| #15 on GitHub |
Technical SEO hygiene: crawl controls, duplicate blog archives and legacy assetsBroad staging SEO, assets and PDF recovery; excludes work transferred to #26–28. GitHub issue: closed. |
13 | Complete |
| #16 on GitHub |
Draft and implement priority solution landing pagesMultiple solution pages staged; hire page, review and QA remain. Completion estimated; excludes later #34 category enhancements. GitHub issue: open. Partial completion is estimated from recorded work. |
13 | 75% |
| #17 on GitHub |
Replace Bellows with accessible sitewide catalogue navigationCustom navigation, integration, accessibility and rollback; subsequent fixes counted separately. GitHub issue: closed. |
13 | Complete |
| #18 on GitHub |
Standardise product-card image and title alignment sitewideSitewide product-card styles and extensive responsive QA. GitHub issue: closed. |
8 | Complete |
| #20 on GitHub |
Redesign About Us on staging with full-width layout and Tremco Pipeline Equipment videoAbout page layout, media and content. GitHub closed as completed; body still contains older review notes. Hire confirmation remains #36. GitHub issue: closed. |
5 | Complete |
| #21 on GitHub |
Redesign Contact page and add sales enquiry form and Google Map on stagingContact layout, form and map staged; delivery and factual review outstanding. Completion estimated. GitHub issue: open. Partial completion is estimated from recorded work. |
5 | 80% |
| #22 on GitHub |
Restore sitewide logo size and header overhang after navigation updateShared logo sizing/alignment correction. GitHub issue: closed. |
2 | Complete |
| #23 on GitHub |
Prevent expanded header navigation flashing during page load on stagingHeader first-paint and mobile alignment fix accepted on staging; issue remains open for release under #29. GitHub issue: open. |
3 | Complete |
| #24 on GitHub |
Fix Browse Equipment expanded-menu flash before JavaScript on stagingCatalogue first-paint fix with delayed/no-script testing. GitHub issue: closed. |
3 | Complete |
| #25 on GitHub |
Redesign and optimise global footer across all webpagesGlobal responsive footer redesign and review. GitHub issue: closed. |
5 | Complete |
| #26 on GitHub |
Production Release: repair leading whitespace in XML sitemapsNarrow sitemap source repair and production validation; completion comment supersedes body. GitHub issue: closed. |
2 | Complete |
| #27 on GitHub |
Investigate shared hosting CPU and process-limit failures on production and stagingHosting diagnosis and staging mitigation pilot; error cause and sustained reliability unresolved. Completion estimated. GitHub issue: open. Partial completion is estimated from recorded work. |
8 | 50% |
| #28 on GitHub |
Release follow-up: reconcile SEO changes, remaining PDF fallbacks and legacy redirectsRemaining PDF restoration, redirect/metadata reconciliation and packaging; predecessor work excluded. GitHub issue: open. |
8 | Pending |
| #29 on GitHub |
Production Release: coordinated staging-to-production site changeoverCoordinated migration, backups, release and live QA; implementation in predecessor tickets excluded. GitHub issue: open. |
8 | Pending |
| #30 on GitHub |
Desktop layout issues: excessive heading spacing and incorrect bevelling page layoutMulti-page spacing/layout corrections and related tracking repairs. GitHub issue: closed. |
3 | Complete |
| #31 on GitHub |
Fix Pipe Bevelling Equipment category label and page text alignmentTargeted category links and alignment repair. GitHub issue: closed. |
2 | Complete |
| #32 on GitHub |
Improve sidebar hierarchy so products are clearly grouped under their categorySidebar hierarchy, automatic collapse and refined transitions. GitHub issue: closed. |
5 | Complete |
| #33 on GitHub |
Audit and fix missing links to subpages across equipment overview pagesBroader audit and link repair across equipment overviews; excludes earlier targeted #31 fix. GitHub issue: closed. |
8 | Complete |
| #34 on GitHub |
Improve equipment category pages with consistent introductions, product navigation and SEOFour category page redesigns, navigation controls and SEO; implementation has not started. GitHub issue: open. |
8 | Pending |
| #36 on GitHub |
Confirm equipment hire inventory and termsClient fact/document confirmation and handoff; waiting time is not effort. GitHub issue: open. |
2 | Pending |
| #37 on GitHub |
Standardise equipment subpages using the approved Sawyer designLarge equipment subpage rollout and responsive/content QA; earlier card/link work excluded. GitHub issue: closed. |
13 | Complete |
| #38 on GitHub |
Audit and fix PDF icons across all pagesFull PDF-icon sweep and fixes recorded; final acceptance review remains. Completion estimated; PDF restoration excluded. GitHub issue: open. Partial completion is estimated from recorded work. |
8 | 90% |
| #41 on GitHub |
Fix SPY portable and in-plant catalogues and match Electrodes stylingTwo SPY catalogue corrections and design matching after #37. GitHub issue: closed. |
3 | Complete |
No tasks match your search.
How this progress estimate is calculated
Overall progress = total earned effort points ÷ total planned effort points.
Each task is assigned relative effort points based on scope, complexity and testing. The scale is 1, 2, 3, 5, 8 or 13; these are weights, not hours. Earned points are the task’s effort multiplied by its completion percentage.
181.75 earned ÷ 228 planned = 79.7%, rounded to 80%. Counting only fully completed task scope gives 147 points, or 64.5%. The overall estimate also credits evidenced work in partially completed tasks.
All effort weights are estimates. Partial completion for tickets #14, #16, #21, #27 and #38 is assessed from recorded work. Ticket #8 explicitly records 60%. Follow-up tickets are weighted for their additional scope to reduce double counting. Waiting time is not effort.
Ticket #23’s staging fix is accepted and counted as complete; its production rollout is covered by #29. Ticket #20 is closed as completed, although its description retains older review notes. The completion comment for #26 confirms its narrow production sitemap repair; the wider release remains pending.
This is a manually prepared snapshot of the assessment dated 9 October 2026, based on 37 discoverable project issues and relevant updates. Draft project cards and exact view filters were not verified. It does not refresh automatically. New scope or revised estimates may change the percentage.
