This document defines the deployment controls, search-engine registration procedures, launch acceptance criteria, and ongoing monitoring activities for https://nowakkamil.com.
The runbook applies to:
- the canonical portfolio at
https://nowakkamil.com/; - Google Search Console;
- Bing Webmaster Tools;
- repository-level SEO and responsive-image validation;
- production crawlability, indexing, structured data, and social metadata.
The privacy and error pages are intentionally excluded from search indexing.
Complete the following checks before each production deployment:
- Run
npm run images:check. - If project source images have changed, run
npm run images:generate, review the generated manifest, and rerunnpm run images:check. - Run
npm run checkto validate TypeScript, linting, formatting, dead code, and responsive images. - Run
npm test. - Run
npm run build. - Confirm that the build validates metadata, canonical URLs, structured data, internal links, the custom 404 page, sitemap, and social image.
- Review
public/sitemap.xml. The sitemap must contain only canonical, indexable URLs.
The image pipeline generates width-based variants according to the dimensions of each source asset. Runtime markup uses srcset, sizes, intrinsic dimensions, lazy loading, and compact fallbacks.
Files under src/assets/projects/responsive/ are generated artifacts and must not be edited manually. Update the source image and run npm run images:generate instead.
Perform this procedure after the SEO implementation is available in production.
- Open Google Search Console.
- Create a Domain property for
nowakkamil.com. - Add the supplied DNS TXT verification record at the authoritative DNS provider.
- Complete ownership verification in Search Console.
- Submit
https://nowakkamil.com/sitemap.xmlin the Sitemaps report. - Run URL Inspection for
https://nowakkamil.com/and request indexing. - Confirm that the Page indexing, HTTPS, and Core Web Vitals reports are available and collecting data.
- Open Bing Webmaster Tools.
- Import the verified Google Search Console property, or verify
nowakkamil.comdirectly through DNS. - Submit
https://nowakkamil.com/sitemap.xmlin the Sitemaps report. - Run a full-domain Site Scan.
- Resolve errors before warnings and informational recommendations.
- Run URL Inspection for the homepage after the first crawl.
IndexNow may be enabled when its key can be stored as a deployment secret and published at the corresponding key URL. API keys and verification secrets must not be committed to the repository.
Record the execution date, environment, and result for each control.
| Control | Expected result |
|---|---|
| Canonical origin | HTTP and www requests redirect once to https://nowakkamil.com/. |
| Unknown route | The response has HTTP status 404 and displays the custom noindex page. |
| Privacy route | /privacy.html redirects to /privacy; the final page declares the extensionless canonical and noindex, follow. |
| Crawler resources | robots.txt and sitemap.xml return HTTP 200. |
| Social image | og.png returns HTTP 200 and has dimensions of 1200脳630 pixels. |
| Progressive enhancement | The homepage retains meaningful professional content when JavaScript or WebGL is unavailable. |
| Structured data | Google Rich Results Test reports no blocking structured-data errors for the homepage. |
| Performance baseline | PageSpeed Insights results are recorded for mobile and desktop. Field data supersedes lab data when sufficient traffic is available. |
| Social metadata | A social-preview debugger displays the expected homepage title, description, and image. |
| Period | Frequency | Required activity |
|---|---|---|
| First four weeks after launch | Weekly | Review indexing, sitemap processing, crawl errors, structured-data status, and Core Web Vitals. |
| Steady state | Monthly | Review search performance, indexed URL count, crawl health, Core Web Vitals, and outstanding recommendations. |
| Material technical release | After deployment | Run URL inspection, verify the sitemap, and repeat the affected production acceptance controls. |
| Control area | Google Search Console | Bing Webmaster Tools | Response criteria |
|---|---|---|---|
| Indexing | Page indexing and sitemap status | Indexed pages and URL Inspection | Investigate any canonical URL reported as blocked, excluded, crawled but not indexed, or assigned an unexpected canonical. |
| Search performance | Queries, pages, countries, and devices | Keywords, pages, clicks, impressions, CTR, and average position | Investigate material changes against the previous comparable period. Changes require sufficient data before corrective action is selected. |
| Technical health | Core Web Vitals, HTTPS, and crawl/index errors | Site Scan and crawl issues | Address errors immediately. Group repeated warnings by shared root cause. |
| Structured data | Enhancements and URL Inspection | Markup and SEO reports | Revalidate JSON-LD after changes to homepage metadata or schema. |
Record the following metrics using consistent 28-day comparison periods:
- clicks;
- impressions;
- click-through rate;
- average position;
- indexed URL count;
- Core Web Vitals status;
- leading search queries;
- leading landing pages;
- crawl or indexing errors;
- unresolved Bing Site Scan findings.
Use 90-day periods for trend analysis and strategic decisions where monthly data volume is insufficient.
Automated reporting may be introduced after the property has accumulated at least 60 days of representative search data.
The reporting integration should:
- use the Google Search Console Search Analytics API and Bing Webmaster APIs;
- use read-only access where supported;
- store credentials in the CI or deployment secret store;
- report by date, query, page, country, and device where available;
- produce 28-day and 90-day comparisons;
- exclude credentials and sensitive raw exports from source control.
OAuth tokens, refresh tokens, API keys, DNS verification values, and sensitive query exports must not be committed to the repository.