Rather than describing SEO work in a CV, this site demonstrates it in a live environment. Every figure published on this page was measured on the live site and can be verified by any visitor.
Results at a glance
| Pages and articles published | 21 |
| Original English copy written | 13,075 words of body copy, measured across those pages |
| Images optimised with keyword filenames and alt text | 31 |
| Internal links written into body copy | 193 |
| URLs listed in the XML sitemap | 24 |
| Authoritative external sources cited in the guides | 15, across the four articles |
| Structured data types implemented | Organization, WebSite, WebPage, BreadcrumbList, Article, Product, FAQPage |
| Google Search Console | Verified, sitemap submitted, indexation monitored |
| Google Analytics 4 | Live and receiving page views |
| PageSpeed Insights – desktop | FCP 0.3 s / LCP 1.1 s / TBT 80 ms / CLS 0.006 |
| PageSpeed Insights – mobile | FCP 0.9 s / LCP 3.0 s / TBT 50 ms / CLS 0.013 |
| Security hardening | XML-RPC, readme.html and license.txt blocked |
How to read this site
If you are an employer
Start with the measurement section below to see how the site is tracked, then open the blog to see how commercial content is written for a B2B audience.
If you are just browsing
The company, the smart switch range and the furniture collections are all fictitious. Nothing on this site is for sale.
What changed after an external review
This site was put in front of an external SEO reviewer who was given no background information. The review found real problems, and the table below records each finding, the change that was made and how the change was verified. It is published on purpose: an audit that finds nothing is not an audit, and correcting your own work is part of the job.
| What the review found | What was changed | How the fix was verified |
|---|---|---|
| The site’s own introduction undercut it. Every page introduced the site as a self-built practice exercise, which framed the whole build as coursework rather than as work. | That wording was replaced site wide with a neutral statement that the company name and product data are fictitious, and this page was rewritten to document the build and its measured results. | All 17 published pages re-crawled and checked for the old wording, including page titles, meta descriptions and the schema output. |
| Structured data was incomplete. Only BreadcrumbList, WebSite, WebPage and Article were being output, and Organization, Product and FAQPage markup were missing. | A brand logo was created and the site representation configured so Organization is emitted, and Product plus FAQPage markup was written for all six product pages, each with a visible FAQ section. | JSON-LD extracted from every page and parsed: two blocks per product page, seven schema types on product pages, zero parse errors. |
| Chinese text left over from a default installation. The breadcrumb label, the default post category, four widget titles and several stored title templates were still in Chinese. | The stored strings and widget titles were replaced with English equivalents, the leftover default category was removed after its post was reassigned, and navigation and date-format leftovers were cleared. | Every published page re-crawled and checked for CJK characters: none found. The old category URL now returns 404 and the sitemap dropped from 25 to 24 URLs. |
| Published figures could not be reproduced. The results table quoted word and internal-link counts that had been measured with inconsistent methods. | Every figure in the results table above was re-measured on the live site using a stated method, and a structured data row was added. | Counts taken directly from the published content, with the measurement basis named in each row. |
How this site was built
- Set up the platform. A self-managed cloud server running Nginx, PHP and MySQL, with WordPress installed by hand rather than through a one-click builder.
- Built the structure. A two-division catalogue – smart switches and furniture – with three product sub-pages under each division, plus service, quality, company and contact pages.
- Wrote the content. Thirteen thousand words of original English copy aimed at importers, wholesalers, distributors and project contractors, including four long-form guides on the blog, each citing primary sources such as the European Commission, the ICC and the US EPA.
- Added and optimised the imagery. Thirty-one images – original product photographs and renders plus the brand logo and site icon – resized, compressed, renamed with English keyword filenames and given descriptive alt text.
- Linked everything together. 193 internal links written into body copy so that related pages reinforce each other instead of competing.
- Configured technical SEO. XML sitemaps, robots.txt, canonical URLs, schema output, HTTPS with automatic renewal and HTTP to HTTPS redirects.
- Connected measurement. Google Search Console verification and sitemap submission, indexation checks page by page, and Google Analytics 4 tracking.
- Hardened the server. Closed unused XML-RPC access, blocked readme.html and license.txt so the platform version is not advertised, and added brute-force protection on SSH.
What was actually done, area by area
- Infrastructure and hosting – domain registration, DNS records, a self-managed cloud server, Nginx, PHP and MySQL, all configured without a website builder.
- HTTPS and SSL – a Let’s Encrypt certificate covering both the root domain and the
wwwversion, automatic renewal, HTTP to HTTPS 301 redirects and HSTS. - Technical SEO – XML sitemaps, robots.txt, canonical URLs, crawlability and indexation control, mobile responsiveness and page speed work.
- Site architecture and internal linking – a two-division category structure with product sub-pages, and internal links written into the body copy of every page so related pages reinforce each other.
- On-page SEO – target keyword selection, title and meta description writing, heading hierarchy and image optimisation with descriptive alt text.
- Content strategy – search intent mapping, keyword clustering and long-form English articles written for B2B buyers.
- Measurement – Google Search Console verification, sitemap submission and index monitoring, plus Google Analytics 4 traffic measurement.
- Security hardening – SSH brute-force mitigation, port rate limiting and closure of unused XML-RPC access.
How the results are measured
Measurement is the part of SEO that is easiest to claim and hardest to prove, so it is documented here in full. Traffic and search visibility are read from Google Search Console and Google Analytics 4, both of which are installed on this domain and collect data continuously. Page speed figures come from Google PageSpeed Insights, tested on the home page on both mobile and desktop, with the raw reports kept as evidence. Indexation is checked page by page through the URL Inspection tool rather than assumed from a sitemap status.
One point worth stating plainly: a sitemap showing a status of “Success” does not mean its pages are indexed, and a page marked “Discovered” is not the same as a page marked “Indexed”. Only the indexed figure in Search Console counts. This site is monitored on that basis.
Why the site is built this way
The content is written as a real B2B manufacturer site would be written, because the skills being demonstrated are the ones a client would pay for: structuring a commercial product range, writing for buyers rather than for search engines, and proving the result with measurable data. See the product pages for the commercial copy, the quality control page for structured long-form content, the OEM and ODM services page for service positioning, and the contact page for a conversion-focused layout.
Disclaimer
All company names, product specifications, prices, certifications, testimonials and case data published on this website are fictitious and are used purely to illustrate SEO, content marketing and independent-site operating practice. Product photography is used to illustrate layout only. No products are offered for sale, and no commercial relationship is implied. Questions about this project are welcome through the contact page.
