Deployment and Authority Operations Checklist

Export dashboard screenshots as WebP after removing student, staff, finance, phone, email, register number, and institution-sensitive details.

Store approved screenshot files under a public-safe asset path and reference them from trust/productProofContent.js only.

Confirm each screenshot has role-specific alt text, category, workflow description, approval date, and reviewer note.

Validate desktop and mobile rendering before publishing, with fallback cards retained for unavailable assets.

Collect written approval from the institution or individual before publishing any quote, role, logo, or reference.

Record source role, institution type, workflow area, approval date, and whether logo/photo use is permitted.

Keep unapproved feedback private and display only role-based trust statements until approval is complete.

Review testimonial wording for operational accuracy, no exaggerated claims, and no private institutional data.

Submit https://necttos.com/sitemap.xml to Google Search Console and Bing Webmaster Tools.

Inspect /, /modules, /resources, /seo-diagnostics, regional pages, authority articles, and case studies after deployment.

Review coverage reports weekly for excluded pages, duplicate canonicals, soft 404s, and crawl failures.

Use search-indexing-report.json after every build to compare route count, duplicate routes, and missing internal links.

Use citation-friendly resources for institutional references, ERP rollout guides, IQAC evidence guides, and principal dashboard guides.

Publish PDF brochures and checklists only after final review, then update downloadableResources with the public file path.

Use webinar and briefing pages for future workshops, search demand capture, and partner/institution sharing.

Keep resource titles stable so backlinks remain valid over time.

Run yarn build before deployment and confirm static generation completes.

Upload dist build and generated public SEO pages according to the deployment process.

Confirm robots.txt, sitemap.xml, search-indexing-report.json, and seo-diagnostics are available on production.

After deployment, test primary routes: /, /modules, /clients, /resources, /seo-diagnostics, /contact, and key SEO pages.

Prepare article, guide, case study, or regional content with target keyword, answer block, FAQ, related links, and schema intent.

Check institutional tone, factual accuracy, privacy safety, internal links, canonical path, and search intent fit.

Add content to the relevant data file, run lint/build, verify sitemap and search-indexing-report.json.

Update content when academic regulations, accreditation requirements, regional targets, or product proof assets change.