Practical guidelines for planning, creating, naming, and delivering content and image assets for the new Degage Corp. website. They establish shared guardrails—not rigid art direction.
Large masterProvide a clean, high-resolution source.
02
Flexible cropProtect the subject across breakpoints.
03
Light deliveryOptimize without visible quality loss.
01
PHASE ONE
Marketing / Creative
Look and feel, page layouts, headers, copy, imagery, photography, and creative handoff standards.
CREATIVE GUIDELINES
These are practical production guardrails, not a requirement to make every page look identical. Creative may recommend a stronger solution when brand, content, or usability benefits—document approved exceptions in the handoff.
Dimensions are delivery targets—not permission to upscale a smaller original. Retain the highest-quality master in the archive.
WHY sRGB?
Because predictable color beats a wider gamut on the web.
sRGB is the safest common display space across browsers, phones, WordPress image processing, and optimization services. It is not the same thing as a HEX code: HEX and RGB are ways to write a color value; sRGB is the color space that tells a screen what that value should look like. Keep the wide-gamut or CMYK master for print; export a converted, embedded sRGB version for the website.
PHOTOSHOP1 Edit → Convert to Profile2 Choose sRGB IEC61966-2.13 File → Export → Export As4 Check Convert to sRGB + Embed Color Profile
Use “Convert to Profile,” not “Assign Profile,” so the visible color is preserved.
Current website reference
Page-by-page asset map
This map reflects the current Degage website. Use it to plan page-specific imagery and content; page names and URLs are reference inputs—not items for Creative to rename.
High/
Home
Hero, 3–4 category cards, process/facility image, social share
High/about-us.php
About Us
Section banner, facility/process set, optional team portrait, social share
High/products.php
Products
Section banner, category cards, product thumbnails, social share
Medium/education.php
Cleanroom Education
Section banner, article lead images, technical diagrams, social share
Low/faq.php
FAQs
Social share only; avoid decorative imagery in the Q&A flow
Creative defines what each page needs. Web / SEO owns URL migration, redirects, canonicals, sitemap updates, and implementation in WordPress.
Selected foundation: Engineer GP Theme
Engineer GP Theme-derived layouts for every page type
Use the Engineer GP Theme starter site for visual language and reusable patterns—not as a reason to force Degage content into a service-company structure.
Delivery sizes—not rendered CSS sizes. Supply the source at the stated pixels and aspect ratio.
COPY COUNTS
Practical target ranges for a first draft. Clarity and completeness matter more than hitting an exact number.
DRAWING KEY
IMAGE Asset placement TEXT Live copy placement
CONCEPTUAL DESIGN DIRECTION
These drawings establish recommended hierarchy, content sequence, image purpose, and approximate composition—not final art direction. Creative may reverse, stack, resize, or recompose sections while preserving required content, asset specifications, accessibility, and conversion priorities.
MOBILE RULE Default to heading → supporting image → copy → CTA. Product detail keeps the product name and essential buying information ahead of secondary gallery images.
GLOBAL SHELL
Engineer GP Theme-style utility/contact bar → Degage logo + navigation → content → RFQ band → structured footer.
PAGE SETTING
Full Width content, no sidebar. Use GeneratePress Elements for global and dynamic templates.
INNER WIDTH
Retain Engineer GP Theme's open composition inside a 1200 px maximum width with 32 / 24 / 20 px responsive gutters.
STYLE SYSTEM
Rebuild Engineer GP Theme's global styles in Degage red, graphite, warm gray, and white before assembling pages.
01
Page
Homepage
/Engineer GP Theme Home — adapted
Global header + navigation
01Value proposition + RFQ heroRECOMMENDED: IMAGE RIGHT
IMAGEDesktop 2400×1200 · Mobile 1080×1350
TEXT / CONTENTEyebrow 2–4 words; H1 6–10; summary 20–35; 1–2 CTA labels at 2–4 words each.
02Standards / trusted-by logo railMARKS IN A ROW
IMAGESVG master · 1000px PNG backup
TEXT / CONTENTSection label 2–5 words; optional intro 15–30; logo names must be live text when needed.
03Quality proof metricsTEXT / DATA ONLY
TEXT / CONTENT3–4 verified statistics; number ≤8 characters; label 2–5 words; context 8–16 words each.
04Company + cleanroom capabilityIMAGE RIGHT
IMAGE1600×1200
TEXT / CONTENTH2 3–8 words; body 60–120; 3–5 bullets at 4–10 words each; optional CTA 2–4 words.
05Product families — card gridTEXT / DATA ONLY
TEXT / CONTENTH2 3–8 words; introduction 20–45; body length determined by the user task.
06Why Degage / reliabilityIMAGE RIGHT
IMAGE1600×1200
TEXT / CONTENTH2 3–8 words; body 60–120; 3–5 bullets at 4–10 words each; optional CTA 2–4 words.
02Standards / trusted-by logo railMEDIAOfficial SVG logos preferred; 1000 px transparent PNG backup. Supply 4–8 approved marks.COPYSection label 2–5 words; optional intro 15–30; logo names must be live text when needed.
03Quality proof metricsMEDIANo image required. Optional simple approved icons as SVG.COPY3–4 verified statistics; number ≤8 characters; label 2–5 words; context 8–16 words each.
04Company + cleanroom capabilityMEDIAPhoto: 1600 × 1200 (4:3), WebP ≤250 KB. Keep subject inside center 70% safe zone.COPYH2 3–8 words; body 60–120; 3–5 bullets at 4–10 words each; optional CTA 2–4 words.
05Product families — card gridMEDIAConfirm during wireframing; use the closest asset specification above.COPYH2 3–8 words; introduction 20–45; body length determined by the user task.
06Why Degage / reliabilityMEDIAPhoto: 1600 × 1200 (4:3), WebP ≤250 KB. Keep subject inside center 70% safe zone.COPYH2 3–8 words; body 60–120; 3–5 bullets at 4–10 words each; optional CTA 2–4 words.
09TestimonialsMEDIAPortrait optional: 800 × 800 (1:1), WebP ≤100 KB; use only with permission.COPYQuote 25–60 words; name 2–4; role/company 2–8. Use 1 featured or 3 short quotes.
10Final quote CTAMEDIANo image required. Optional subtle background texture under 100 KB.COPYH2 4–9 words; support 12–30; one primary CTA at 2–4 words; optional phone number.
02
Page
About Us
/about-us.phpEngineer GP Theme About — adapted
Global header + navigation
01Page title + concise promiseRECOMMENDED: IMAGE RIGHT
02Company storyMEDIANo image required unless the content specifically benefits from one.COPYH2 3–8 words; body 60–150; paragraphs 25–70; optional bullets at 4–12 words.
03Industries and applicationsMEDIACard image optional: 1200 × 900 (4:3), WebP ≤140 KB. Keep all cards in the set consistent.COPY3–6 cards; title 2–7 words; body 15–35; CTA 2–4 words per card.
04Facility / process photographyMEDIAPhoto: 1600 × 1200 (4:3), WebP ≤250 KB. Keep subject inside center 70% safe zone.COPYH2 3–8 words; body 60–120; 3–5 bullets at 4–10 words each; optional CTA 2–4 words.
05Quality metricsMEDIANo image required. Optional simple approved icons as SVG.COPY3–4 verified statistics; number ≤8 characters; label 2–5 words; context 8–16 words each.
03Search, filters + result countMEDIANo image required; use live icons only when they add meaning.COPYLabels 1–5 words; instructions 8–20 when needed; keep controls concise and descriptive.
05PaginationMEDIANo image required; use live icons only when they add meaning.COPYLabels 1–5 words; instructions 8–20 when needed; keep controls concise and descriptive.
04Comparison specificationsMEDIANo image required. Use live accessible HTML tables; never flatten specifications into an image.COPYIntro 20–40 words; row labels 1–6 words; values + units only; table note 10–30 words when required.
05Relevant standardsMEDIAOfficial SVG marks preferred; transparent PNG backup at 1000 px wide. Verify usage permission.COPY3–8 items; label 2–6 words; optional explanation 12–25 words each.
TEXT / CONTENT3–6 approved product questions; question 6–14 words; answer 30–100. Place after specifications and configurations.
07Related productsIMAGE ABOVE CARD COPY
IMAGEProduct 1600×1600 · Category 1200×900
TEXT / CONTENTSection H2 3–8 words; intro 20–40; card title 2–7; summary 15–30; CTA 2–4 words.
08Request a quote CTATEXT / DATA ONLY
TEXT / CONTENTH2 4–9 words; support 12–30; one primary CTA at 2–4 words; optional phone number.
Engineer GP Theme does not provide the required technical product record. Build one dynamic template from structured fields so every product stays consistent.
BUILD WITHGP Content Template + dynamic GB fields
Section deliverables
01BreadcrumbsMEDIANo image required; use live icons only when they add meaning.COPYLabels 1–5 words; instructions 8–20 when needed; keep controls concise and descriptive.
03Standards / certification badgesMEDIAOfficial SVG logos preferred; 1000 px transparent PNG backup. Supply 4–8 approved marks.COPYSection label 2–5 words; optional intro 15–30; logo names must be live text when needed.
04Specifications tablesMEDIANo image required. Use live accessible HTML tables; never flatten specifications into an image.COPYIntro 20–40 words; row labels 1–6 words; values + units only; table note 10–30 words when required.
03Topic navigationMEDIANo image required; use live icons only when they add meaning.COPYLabels 1–5 words; instructions 8–20 when needed; keep controls concise and descriptive.
05PaginationMEDIANo image required; use live icons only when they add meaning.COPYLabels 1–5 words; instructions 8–20 when needed; keep controls concise and descriptive.
06Ask a technical question CTAMEDIANo image required. Optional subtle background texture under 100 KB.COPYH2 4–9 words; support 12–30; one primary CTA at 2–4 words; optional phone number.
07
Single Article
Education Article
/education/[article-slug]/Engineer GP Theme Single Post — adapted
Global header + navigation
01Breadcrumb + article headerRECOMMENDED: IMAGE RIGHT
02Lead image / diagramMEDIAPhoto: 1600 × 900 (16:9), WebP ≤200 KB. Diagram: SVG preferred or PNG at 2× display size.COPYCaption 8–20 words when informative; source / figure note 5–15 words.
03Article body + jump linksMEDIAInline images: 1600 px wide; diagrams SVG preferred. Use only when they explain a technical point.COPYUsually 700–1,500 words; 25–60-word opening answer; H2 every 150–300 words; paragraphs 25–70 words.
04Standards / source notesMEDIANo image required unless the content specifically benefits from one.COPYH2 3–8 words; body 60–150; paragraphs 25–70; optional bullets at 4–12 words.
05Optional contextual FAQsMEDIANo image required. Omit the entire block when it would repeat the article.COPYOptional 3–5 recurring questions; question 6–14 words; answer 30–100. Keep the article’s main answer in the body.
07Technical help CTAMEDIANo image required. Optional subtle background texture under 100 KB.COPYH2 4–9 words; support 12–30; one primary CTA at 2–4 words; optional phone number.
TEXT / CONTENTLabels 1–5 words; instructions 8–20 when needed; keep controls concise and descriptive.
03Grouped question accordionsTEXT / DATA ONLY
TEXT / CONTENT8–20 questions; question 6–14 words; answer 30–100; link text 2–6 words when useful.
04Related educationIMAGE ABOVE CARD COPY
IMAGEDesktop 1600×900 · Mobile 1200×1200
TEXT / CONTENTSection H2 3–8 words; card title 6–12; excerpt 20–35; CTA 2–4 words.
05Unanswered question CTATEXT / DATA ONLY
TEXT / CONTENTH2 4–9 words; support 12–30; one primary CTA at 2–4 words; optional phone number.
Engineer GP Theme has no dedicated FAQ layout. Reuse its page title, spacing, typography, card treatment, and CTA while keeping answers as indexable text.
02Topic jump linksMEDIANo image required; use live icons only when they add meaning.COPYLabels 1–5 words; instructions 8–20 when needed; keep controls concise and descriptive.
03Grouped question accordionsMEDIANo image required.COPY8–20 questions; question 6–14 words; answer 30–100; link text 2–6 words when useful.
02Contact methods + RFQ formMEDIAOptional facility image: 1600 × 1200 (4:3), WebP ≤250 KB. No decorative image is required.COPYH2 3–8 words; intro 20–45; field labels 1–5; helper text 8–20; submit label 2–4 words.
03Quote preparation checklistMEDIACard image optional: 1200 × 900 (4:3), WebP ≤140 KB. Keep all cards in the set consistent.COPY3–6 cards; title 2–7 words; body 15–35; CTA 2–4 words per card.
04Facility / service informationMEDIAPhoto: 1600 × 1200 (4:3), WebP ≤250 KB. Keep subject inside center 70% safe zone.COPYH2 3–8 words; body 60–120; 3–5 bullets at 4–10 words each; optional CTA 2–4 words.
05Response expectationMEDIANo image required. Optional subtle background texture under 100 KB.COPYH2 4–9 words; support 12–30; one primary CTA at 2–4 words; optional phone number.
10
Utility Page
Standard Content
/privacy-notice.php · /sitemap.phpEngineer GP Theme inner-page shell
02Updated date / jump linksMEDIANo image required; use live icons only when they add meaning.COPYLabels 1–5 words; instructions 8–20 when needed; keep controls concise and descriptive.
03Narrow text contentMEDIAConfirm during wireframing; use the closest asset specification above.COPYH2 3–8 words; introduction 20–45; body length determined by the user task.
04Helpful linksMEDIACard image optional: 1200 × 900 (4:3), WebP ≤140 KB. Keep all cards in the set consistent.COPY3–6 cards; title 2–7 words; body 15–35; CTA 2–4 words per card.
11
System
System States
/search/ · /404/ · /thank-you/Custom states in Engineer GP Theme styles
02Results or confirmation messageMEDIANo image required unless the content specifically benefits from one.COPYH2 3–8 words; body 60–150; paragraphs 25–70; optional bullets at 4–12 words.
03Search / next actionMEDIANo image required; use live icons only when they add meaning.COPYLabels 1–5 words; instructions 8–20 when needed; keep controls concise and descriptive.
04Helpful product-family linksMEDIACard image optional: 1200 × 900 (4:3), WebP ≤140 KB. Keep all cards in the set consistent.COPY3–6 cards; title 2–7 words; body 15–35; CTA 2–4 words per card.
05Contact CTAMEDIANo image required. Optional subtle background texture under 100 KB.COPYH2 4–9 words; support 12–30; one primary CTA at 2–4 words; optional phone number.
Designer handoff ruleProvide content and assets by section name. The web designer owns the final block assembly, responsive settings, alt text entry, schema, links, and accessibility checks in WordPress.
Creative copy system
Content standards
Preserve approved product names, codes, and verified facts exactly. Creative improves the supporting headers, summaries, section hierarchy, calls to action, and explanations around them.
01
Technical and plain
Write for engineers, purchasers, quality teams, and operations staff. Explain specialized terms on first use and remove filler.
02
Proof before promotion
Use specific materials, applications, standards, test results, and service capabilities instead of unsupported superlatives.
03
Approved names stay fixed
Use every approved product name and product code exactly as supplied. Do not shorten, modernize, optimize, or rewrite them.
04
Reviewed and current
Every technical claim and document needs an owner, source, approval status, revision date, and scheduled review.
Product title treatment
DC-1200-CT Cleanroom Poly Tubing
Virgin LDPE tubing for ISO Class 5 cleanroom packaging applications.
Virgin LDPEISO Class 52–8 milLay-flat tubing
LOCKED: use the approved product name and product code exactly as supplied. Improve clarity with supporting copy, badges, specifications, and page hierarchy—not by renaming the product.
USE
Specific, measurable language: “Available in 2, 3, 4, 6, and 8 mil.”
AVOID
“Best,” “highest quality,” “medical grade,” or “FDA approved” unless the exact statement is documented and approved.
STYLE
Sentence case, short paragraphs, descriptive headings, active voice, and one clear action per section.
HOME
Lead with relevance
One clear value proposition, product families, industries served, documented proof, quality capabilities, education, and a visible RFQ action.
PRODUCT CATEGORY
Help buyers choose
Overview, applications, selection guidance, product grid, comparison data, applicable standards, related education, and category RFQ.
PRODUCT DETAIL
Make facts scannable
Code, summary, applications, material, configurations, verified standards, specification tables, current documents, related products, and RFQ.
EDUCATION
Answer first
State the answer early, use descriptive headings and diagrams, cite sources, show author/reviewer and update date, then link relevant products.
FAQ
Be direct
Use the customer's natural-language question. Answer it in the first sentence, then add context, limitations, and a useful next link.
ABOUT + CONTACT
Build confidence
Use verifiable history and capabilities. RFQ forms should collect family, dimensions, thickness, quantity, standard, timeline, and attachments.
01
Specifications
Use accessible HTML tables with column headings, consistent units, and meaningful empty states. Never substitute bullets or zeros for unknown values.
02
Documents
Publish approved SDS, test reports, guarantees, and certificates as dated PDFs with title, document type, revision number, and file size.
03
Claims
Record the source for every compliance, cleanliness, performance, safety, environmental, and material claim. Technical approval is required before publishing.
04
Terminology
Maintain an approved glossary for cleanroom, ISO Class 5, LDPE, mil, antistatic, static shielding, product codes, test methods, and legacy names.
05
Links
Use descriptive link text. Connect product families to products, education to relevant products, and technical terms to supporting explanations.
06
Images
Creative supplies subject and purpose notes. The web designer writes final contextual alt text, enters it in WordPress, and leaves decorative images empty.
KEEP
Verified product codes, materials, dimensions, configurations, test methods, useful applications, and authoritative documents.
REWRITE
Introductions, category descriptions, FAQs, calls to action, supporting headings, metadata, and unclear technical explanations. Never rewrite approved product names or codes.
MERGE
Overlapping blog posts, duplicate category copy, repeated standards explanations, and near-identical application pages.
RETIRE
Unsupported claims, obsolete documents, inaccurate facts, thin posts, broken external assets, and content with no user or search value.
Required approval flowProduct / technical owner verifies facts and documentsContent owner writes and organizes the copyWeb designer builds, links, formats, and enters alt textFinal review checks accuracy, accessibility, SEO, and redirects
Product-name rule: product names and codes are controlled source information. Any requested change must come from the authorized Degage product owner—not from Creative, Web, or SEO.
Conversion guidance
CTA standards + page word-count goals
Give buyers a clear next step throughout the journey. Repeat the primary action at useful decision points without turning every section into a sales pitch.
01
One primary action
Use Request a Quote consistently as the principal conversion action across commercial pages.
02
Repeat, don’t multiply
Most pages need 2–4 placements of the same primary CTA—not several competing actions with equal emphasis.
03
Match buyer intent
Use lower-commitment labels such as View Product, View Specifications, or Ask a Technical Question when appropriate.
04
Keep labels direct
Target 2–5 words. Add a short support line when users need to know what happens after clicking.
Homepage3–4Request a QuoteHero · after product families · proof section · final CTA
Products archive2–3Get Product HelpArchive intro · after product grid · final selection-help CTA
Product category2–3Request a QuoteCategory intro · after comparison or grid · final CTA
Product detail3Request a QuoteAbove fold · after specifications · page end; sticky on mobile
Education1–2Ask a Technical QuestionRelated-product context · article or archive end
About Us2Talk to a RepresentativeAfter capabilities · page end
FAQs2Still Have a Question?After major question groups · page end
Contact / RFQ1Submit RequestOne clear form action; avoid competing buttons
Editorial planning
Recommended unique body-copy ranges
Targets exclude global navigation, footer copy, repeated legal language, and structured technical data unless noted.
Homepage500–900 words
Value proposition, proof, product-family introductions, and CTA support.
About Us600–1,000 words
History, facility, capabilities, quality process, and industries served.
Products archive300–600 words
Unique archive introduction and selection guidance; product-card copy is separate.
Product category500–900 words
Overview, applications, selection guidance, comparisons, and standards.
Product detail350–700 words
Unique narrative copy; structured specifications and document titles are separate.
Education archive200–400 words
Purpose, topic navigation, and editorial context; article excerpts are separate.
Education article800–1,500 words
Answer-first technical article with sources, diagrams, and useful subheads.
FAQs600–1,500 words
Usually 8–20 useful questions; length follows the number of approved answers.
Contact / RFQ250–500 words
Instructions, response expectations, contact details, and form guidance.
Utility pagesAs needed
Completeness and legal accuracy matter more than a target range.
System states50–200 words
Clear status, next step, and helpful links for search, 404, and thank-you pages.
These are drafting goals—not SEO quotas. Use the shortest copy that fully answers the user’s questions and supports a decision. Never pad a page to hit a number, and never alter approved product names or codes.
WEB / SEO HANDOFF
Web / SEO owns form behavior, mobile sticky controls, event tracking, confirmation pages, conversion reporting, and testing. Creative owns CTA hierarchy, label, support copy, and placement intent.
File hygiene
Naming & delivery
Use a short, descriptive filename so the asset is identifiable in WordPress and from its URL. Filenames provide a minor image-search signal, but they do not replace accurate alt text or relevant page content. Never keyword-stuff filenames.
Photos and most graphics. Export at 75–85 quality, then inspect at 100%.
JPG
Fallback & social
Use for photography when a platform does not reliably accept WebP.
PNG
Transparency only
Use for product cutouts or logos requiring alpha. Never use for ordinary photos.
SVG
Logos & icons
Outline fonts, remove hidden layers, and provide an editable master separately.
Art direction
Make clean feel credible.
Every photograph should communicate precision, material quality, and a controlled environment—not generic stock photography.
SAFE ZONE
Keep key product details within the center 60%
01Light cleanlySoft, even light; retain edge detail in clear film.
02Show scaleInclude a measured reference or contextual view when size is not obvious.
03Control reflectionsAvoid clipped highlights, fingerprints, dust, and unintended glare.
04Stay accurateColor, seams, closures, and thickness cues must represent the actual product.
Before you submit
Creative preflight
Complete all eight checks for every final asset package.
0%ready
DELIVERY PACKAGE
01 / Masters Layered or raw sources
02 / Web Named, optimized exports
03 / Handoff Alt text + rights notes
02
PHASE TWO
Web / SEO
WordPress implementation, structured fields, final alt text, metadata, schema, URLs, redirects, accessibility, and performance.
GeneratePress + GenerateBlocks
Product template system
Build the design once, then populate it from WordPress product records. The product archive and every product detail page should share the same data model.
GeneratePress site container1200 pxAppearance → Customize → Layout → Container
GenerateBlocks global max-width1200 pxUse on every inner section container
Pagination: indexable numbered pages. Avoid infinite scroll as the only route to products.
02
Single product template
DC-1200-CT example
Hero: breadcrumbs, product code, short H1, one-paragraph value proposition, certification badges, and Request a Quote.
Layout: 44% image gallery / 56% product copy, 48 px gap; stack image first on tablet and mobile.
Primary image: 1600 × 1600, 1:1, neutral background, 10% clear space. Add 2–4 detail images only when useful.
Specifications: scannable two-column tables for material, format, clarity, thickness, standards, and physical properties.
Documents: move the long safety sheet out of body copy into a dated, accessible PDF download with revision number.
Contextual FAQs: include 3–6 approved product questions after specifications and configurations; keep every answer visible and match any FAQPage markup exactly.
Finish: related products from the same taxonomy and a second quote CTA.
THE WORDPRESS MODEL
Custom post type: Product
Taxonomies: Product family, material, format, cleanroom class
REUSABLE FIELDS
Product code · short description · featured image · gallery · standards · thickness · material · configurations · documents
BLOCK ASSEMBLY
GeneratePress Block Elements for archive/single templates when GP Premium is available; GenerateBlocks Container, Grid, Query Loop, Image, Headline, and Button blocks for layout and dynamic content.
Do not paste each product into a one-off page.Structured fields keep cards, filters, schema, related products, and future updates consistent.
Accessibility + SEO
Write alt text for the job
Describe what matters in context. Don’t repeat the caption, start with “image of,” or stuff keywords.
Good
“Clear Class 100 polyethylene bag with heat-sealed bottom.”
Specific, concise, and useful when the image is unavailable.
Keyword-heavy, unnatural, and missing the image’s actual content.
Decorative
Use an empty alt attribute: alt=""
Only when the image adds no information and nearby text already provides the meaning.
Web / SEO content pattern
Contextual FAQs + schema
Add FAQs when they remove a real buying or technical obstacle. They support the page’s primary content; they do not replace product summaries, applications, specifications, standards, documents, or quote actions.
01
Answer real questions
Use questions heard by sales, customer service, technical staff, and customers. One clear answer per question.
02
Keep core sections
Specifications, configurations, applications, standards, downloads, and RFQ guidance remain visible and structured.
03
Match visible content
Any FAQPage structured data must reproduce the exact question and answer that a visitor can read on the page.
04
Avoid duplication
Place an answer on the most relevant page. Link to it elsewhere instead of repeating the same FAQ across the site.
Page typeQuestionsPlacementRecommended focus
Product detail3–6After specifications and configurations; before related products or the final CTA.Sizing, materials, custom options, lead-time process, cleanroom use, and documents.
Product category4–8After selection guidance or the comparison table; before the final category CTA.How to choose, material differences, applications, standards, and custom capabilities.
Education articleOptional 3–5Near the conclusion, only when several recurring questions remain after the article.Clarifications that support the article; do not repeat the body copy.
Central FAQ8–20Group by topic with jump links, related resources, and a final contact action.Company-wide buying, service, quality, ordering, and technical questions.
Home / About / ContactUsually noneAdd only when a repeated question blocks the page’s primary user task.Do not add a generic FAQ section simply to increase word count or schema.
PRIMARY PAGE SCHEMA
Product + Breadcrumb
Use accurate Product data on product pages and Breadcrumb data across the page hierarchy. Add Offer only when visible price and availability are genuinely maintained.
CONDITIONAL
FAQPage
Use only when the page visibly contains company-authored questions with one approved answer each. Schema is machine-readable context, not a promised search feature.
DO NOT USE HERE
QAPage
Reserved for a single question where users can submit alternative answers. It is not the correct type for Degage-authored FAQ lists.
Do not sell FAQs as a rich-result tactic. Google generally limits FAQ rich results to authoritative government and health sites. Keep FAQs because they help buyers and clarify the page—not because an expanded search display is guaranteed. Review Google’s current FAQ guidance ↗
OWNERSHIP
Creative / Content proposes the question hierarchy and drafts plain-language answers. Product / Technical verifies every claim. Web / SEO removes duplication, places the block, implements matching JSON-LD, validates it, and monitors search reporting.
Web / SEO implementation
SEO standards for migration and launch
Preserve existing search equity, make every page understandable to people and search engines, and measure the migration after launch.
01
Use descriptive product URLs
Recommended: /products/dc-1200-ct-cleanroom-poly-tubing/. Short, lowercase, hyphenated, and stable.
02
Preserve product names
Use the approved product name and code unchanged in the H1 and structured data. Improve search clarity through supporting copy, specifications, metadata, and page structure.
03
Write unique search snippets
Give each indexable page a concise title and useful meta description. Lead with the approved product name, then distinguish the application or benefit.
04
Control indexation
Use one self-referencing canonical per preferred page. Noindex internal search, thin filter combinations, staging pages, and other duplicate states.
05
Add product semantics
Use Product structured data with accurate name, SKU, brand, description, and images. Add Offer only when price and availability are genuinely displayed.
06
Strengthen internal links
Link Home → product families → products, Education → relevant products, and products → related education using descriptive anchor text.
07
Optimize images responsibly
Use descriptive filenames, contextual alt text, explicit dimensions, responsive sources, and lazy loading below the fold. Visual quality still comes first.
08
Measure the migration
Submit the XML sitemap in Search Console, inspect priority pages, monitor indexing and 404s, and compare organic landing-page performance after launch.
Ownership: Web / SEO implements and validates these requirements. Creative supplies approved copy, hierarchy, imagery, and subject notes; SEO review must not rename approved products.