Google Merchant titles and descriptions for WooCommerce

WooCommerce product title and description optimization for Google Merchant Center

A WooCommerce product title may look clear inside an online store but still provide insufficient information for Google Merchant Center.

A product description may contain several paragraphs, technical specifications and sales language while failing to identify the exact item Google is expected to process.

Product title and description optimization is therefore not the practice of adding as many search terms as possible. It is the process of creating accurate, differentiated and consistent product information that helps customers and Google understand exactly what is being sold.

A reliable optimization process must consider:

• The real product identity
• The WooCommerce product name
• The submitted Merchant title
• The long and short WooCommerce descriptions
• The selected product variation
• Brand and manufacturer information
• Product identifiers
• Important attributes
• The target country
• The content language
• The public landing page
• Structured product data
• The Merchant Center processed result

The objective is not to make every title longer or every description more promotional.

The objective is to supply the most useful truthful information in an order that clearly distinguishes the product from other items in the catalogue.

Google independently decides how submitted product data is processed and displayed. An optimized title or description cannot guarantee approval, impressions, clicks, advertising performance or sales.

The short answer

A dependable WooCommerce Google Merchant title and description optimization workflow consists of the following steps:

1. Identify the exact WooCommerce product or variation.
2. Record the current product name and descriptions.
3. Determine which WooCommerce fields the Merchant integration uses.
4. Identify the brand, product type, model and distinguishing attributes.
5. Remove unsupported, promotional and irrelevant statements.
6. Put the most important product-identifying information first.
7. Create a unique title for each separately submitted product.
8. Include applicable variation attributes in variation titles.
9. Write a factual description about the submitted product only.
10. Match the title and description with the public landing page.
11. Use the correct language for the target product data.
12. Confirm that attributes such as colour and size use consistent values.
13. Inspect structured product data.
14. Check for theme, SEO and schema-plugin conflicts.
15. Update the authoritative WooCommerce source.
16. Clear relevant caches.
17. Submit the corrected product through the active data source.
18. Confirm that Merchant Center processed the new information.
19. Review item-level issues and destination status.
20. Compare performance only after sufficient stable data has accumulated.

Title and description optimization should improve clarity without changing the identity, condition, contents or commercial meaning of the product.

Understand what the Merchant product title represents

The Merchant title identifies the individual product offer.

It is not automatically the same as:

• The WordPress page title
• The browser title tag
• The SEO title
• The WooCommerce menu label
• The product slug
• The category name
• The manufacturer’s marketing slogan
• The name of a product group
• The Merchant offer ID

In many WooCommerce integrations, the product name is used as the initial Merchant title. However, another field, custom mapping, product rule or integration-specific value may override it.

Before editing hundreds of products, determine which field is actually being submitted.

For one product, record:

• WooCommerce product ID
• Variation ID where applicable
• SKU
• Merchant offer ID
• WooCommerce product name
• SEO title
• Submitted Merchant title
• Processed Merchant title
• Public page heading
• Structured-data product name
• Active data-source name

If these values differ, identify which difference is intentional and which one reflects an old mapping, cache or competing source.

Do not assume that changing an SEO title automatically changes the Merchant title.

Google’s title requirements

Google’s current product data specification allows a maximum of 150 characters for the title attribute.

The title should accurately describe the product and match the product shown on the landing page.

Google advises merchants not to include:

• Promotional statements such as “free shipping”
• Excessive capital letters
• Gimmicky foreign characters
• Information that does not describe the product
• Misleading product attributes
• Terms belonging to another product or variation

Google’s specific title attribute guidance recommends using a relevant title that clearly describes the product. Although up to 150 characters can be supplied, the complete title may not always be displayed.

The beginning of the title therefore carries particular importance.

The title should not be filled to 150 characters merely because that space is available.

A shorter title can be better when it identifies the product completely. A longer title is useful only when the added information is accurate, distinguishing and relevant.

Put the most important product information first

Customers can encounter a shortened product title on smaller screens and different Google surfaces.

The first part should answer the most important identification questions:

• What is the product?
• What brand is it?
• Which model or product line is it?
• Which variation is being offered?
• What essential characteristic distinguishes it?

The appropriate order depends on the product category.

A useful general structure is:

Brand + product type + model + important characteristic + variation

For example:

Acme TrailPro Waterproof Running Shoes – Black – EU 42

This title identifies:

• Brand: Acme
• Product line: TrailPro
• Product type: Running shoes
• Relevant feature: Waterproof
• Colour: Black
• Size: EU 42

The same structure is not suitable for every product.

A book may need:

Title + author + format + edition

A replacement part may need:

Brand + compatible model + part type + part number

Furniture may need:

Brand + product type + material + colour + size

Food products may need:

Brand + product type + flavour + quantity or net content

Electronics may need:

Brand + model + product type + capacity + colour

Use the structure that describes the actual product rather than forcing every catalogue item into one generic formula.

Avoid treating product titles as keyword containers

Search relevance does not justify adding unrelated search phrases.

A title such as:

Best Cheap Men’s Shoes Sneakers Trainers Sports Footwear Sale Free Shipping

does not clearly identify one product.

It combines:

• Subjective claims
• Repeated synonyms
• Promotional language
• Shipping information
• Broad search phrases
• No reliable model or variation identity

A clearer title would be:

Acme RunLite Men’s Road Running Shoes – Navy – EU 43

The improved title uses fewer words but provides stronger product identity.

Do not add:

• Competitor brand names
• Search terms that do not appear on the product page
• Unverifiable superlatives
• “Best”
• “Cheapest”
• “Number one”
• “Guaranteed”
• “Official” without legitimate support
• “Google approved”
• “Limited offer”
• “Buy now”
• “Free shipping”
• Price or discount messages
• Repeated category synonyms

Google’s product-data optimization guidance advises merchants to use product titles and descriptions that agree with the landing page rather than adding synonyms or search terms absent from that page.

The product must first be described truthfully. Search relevance should come from accurate product characteristics.

Create a distinct title for every submitted product

Every separately submitted product should be identifiable.

A WooCommerce catalogue can contain several products named:

• Classic shirt
• Standard cable
• Replacement filter
• Coffee mug
• Office chair
• Phone case

These titles may be understandable to the store administrator but insufficient for distinguishing Merchant offers.

A more useful title adds authentic identifying information.

Examples:

Northbay Men’s Classic Oxford Shirt – White – Slim Fit

Voltix USB-C to USB-C Charging Cable – 2 m – Black

PureAir HEPA Replacement Filter for PA-300

Cerama Stoneware Coffee Mug – 350 ml – Sage Green

ErgoLine Mesh Office Chair with Adjustable Lumbar Support – Black

ShieldPro Case for Pixel 10 – Clear

Do not add attributes that are not verified.

If the cable does not support a stated charging speed, do not insert one merely because customers search for it.

If a phone case is compatible with only one model, do not list several related models.

Optimize variable product titles carefully

A variable WooCommerce product can create multiple Merchant offers.

Each variation may have a separate:

• Variation ID
• SKU
• Merchant offer ID
• Colour
• Size
• Material
• Pattern
• Capacity
• Pack quantity
• Image
• Price
• Availability

Google’s product specification advises merchants to include distinguishing characteristics such as colour or size for variants.

Consider a WooCommerce parent product named:

Women’s Linen Shirt

The submitted variations could use titles such as:

• Northbay Women’s Linen Shirt – White – Small
• Northbay Women’s Linen Shirt – White – Medium
• Northbay Women’s Linen Shirt – Blue – Small
• Northbay Women’s Linen Shirt – Blue – Medium

The parent identity remains consistent, while each submitted variation becomes distinguishable.

Do not add a variation attribute when it does not apply to the specific offer.

A blue variation should not inherit “red” from:

• The default variation
• An old product name
• A cached SEO title
• The parent image
• A manual Merchant rule
• Another data source

The landing-page URL should also open or clearly represent the submitted variation.

A descriptive variation title cannot compensate for a landing page that selects a different colour or displays a different price.

Keep variation naming consistent

Use one naming system throughout a variation group.

Avoid mixtures such as:

• Small
• M
• Large size
• XL
• Extra Large
• X-large

The public page, submitted product data and relevant structured attributes should use a clear and consistent system.

The same principle applies to colour.

Avoid changing an authentic colour name only to target a broader phrase.

If the WooCommerce page calls the product colour “Midnight Sky,” the submitted data should not silently call it “Dark Blue” while the public page retains the original name.

If clarification is genuinely needed, publish the clarification consistently on the product page and in the submitted data.

Understand the role of the product description

The Merchant product description should explain the actual product.

It is not the place for:

• A company history
• A category introduction
• Shipping promises
• Payment instructions
• Return-policy text
• Competitor comparisons
• Links to other products
• Links to the store
• Keyword lists
• Coupon codes
• Advertising slogans
• Customer testimonials
• Unsupported health or performance claims

Google permits up to 5,000 characters for the standard description attribute. Google’s guidance for short product descriptions recommends approximately 500–1,000 characters while still allowing up to 5,000 characters.

This does not mean that every description must reach 1,000 characters.

The correct length depends on the information genuinely needed to describe the product.

A simple cable may require fewer details than:

• A computer
• A machine component
• A piece of furniture
• A professional tool
• A technical appliance
• A product bundle

The description should be long enough to identify and explain the item but not padded with repeated text.

Write descriptions around product facts

A useful description can cover:

• Product type
• Intended purpose
• Brand and model
• Primary material
• Important dimensions
• Capacity
• Compatibility
• Included components
• Colour
• Pattern
• Construction
• Essential technical features
• Care instructions
• Installation requirements
• Age range where relevant
• Product condition
• Pack contents
• Limitations necessary to understand the product

For example:

The Voltix C200 is a 2-metre USB-C to USB-C cable designed for compatible phones, tablets and laptops. It has a braided black outer layer, reinforced connector housings and USB-C connectors at both ends. The package contains one cable. Charging speed and data-transfer performance depend on the connected devices and power adapter.

This description explains the product without introducing:

• A discount
• Shipping information
• Competitor comparisons
• Unsupported speed claims
• Unrelated accessories
• A guarantee not shown on the website

Place essential description details early

Google may display only part of the supplied description.

The opening should therefore identify the product and its most useful characteristics.

Avoid beginning every description with generic language such as:

• Welcome to our store
• Discover unmatched quality
• We are proud to present
• This amazing product will change your life
• Buy today and save
• The best solution for everyone

A factual opening is more useful:

The Northbay TrailPro is a waterproof men’s running shoe with a rubber outsole, removable insole and lace closure.

The customer immediately knows what the product is.

Supporting details can follow.

Use natural language instead of keyword repetition

A description should read as product information, not as a search-term list.

Poor example:

Running shoes men, men running trainers, sports shoes, waterproof shoes men, black running shoes, best running footwear.

Improved example:

The Acme TrailPro is a black waterproof running shoe designed for men. It has a breathable textile upper, rubber outsole, removable insole and lace closure. This offer is for EU size 42.

The second version contains meaningful terms in a natural context and identifies the exact variation.

Do not repeat the product name or the same attribute merely to increase keyword frequency.

Repetition can make the content less useful and can introduce inconsistencies during later catalogue updates.

Match the WooCommerce landing page

Google recommends using product titles and descriptions that correspond with the product landing page.

This does not require every surrounding page element to be identical character for character. However, the page and submitted data should clearly describe the same product.

Check:

• Product name
• Brand
• Model
• Product type
• Variation
• Colour
• Size
• Material
• Capacity
• Pack quantity
• Compatibility
• Condition
• Included components
• Important limitations

The submitted title should not describe a three-piece set if the landing page sells one item.

The description should not say that a charger is included when the product page states that it is sold separately.

A submitted title should not describe a new product when the page sells a refurbished product.

A Merchant-specific title mapping can be legitimate, but its content must remain supported by the public product page.

Distinguish the WooCommerce long description from the short description

WooCommerce can store:

• Product name
• Long description
• Short description
• Attribute values
• Variation descriptions
• Custom fields
• SEO title
• Meta description

The Merchant integration may use one or combine several of these fields.

Do not assume that the visible short description is the submitted Merchant description.

Test one product and compare:

1. WooCommerce long description
2. WooCommerce short description
3. SEO meta description
4. Integration preview
5. Submitted Merchant value
6. Merchant Center processed value

If the submitted description contains navigation text, shortcodes, HTML fragments or unrelated page content, inspect the selected source field and sanitization process.

A change should be made in the field intended to remain authoritative.

Remove page-builder and shortcode residue

WooCommerce descriptions created with page builders can contain:

• Shortcodes
• Reusable-block markers
• Button text
• Accordion labels
• CSS class names
• Form text
• Tracking fragments
• Broken HTML
• Image captions
• Template placeholders

The public page may render these elements correctly while an integration extracts unsuitable raw content.

For example, a submitted description should not contain:

[button url="/contact"]Ask for price[/button]

or:

tab_title="Technical details"

Inspect the actual Merchant input rather than relying only on the rendered WooCommerce page.

When necessary, use a clean product-data field specifically mapped for Merchant communication, provided that the mapped description still agrees with the public landing page.

Keep formatting controlled

Google permits formatting such as line breaks and lists in supported descriptions, but the submitted content should remain readable after processing.

Use formatting to separate:

• Main product explanation
• Materials
• Dimensions
• Included items
• Care instructions
• Compatibility

Do not depend on complex HTML, scripts, interactive tabs or styling to communicate essential product facts.

The information should remain understandable as plain product text.

Separate product descriptions from other attributes

Not every detail should be repeated inside the description.

Merchant product data can contain separate attributes for:

• Brand
• GTIN
• MPN
• Colour
• Size
• Material
• Pattern
• Age group
• Gender
• Product type
• Google product category
• Product details
• Product highlights
• Multipack
• Bundle status

The product detail attribute can provide structured technical specifications not represented by another dedicated attribute.

The product highlight attribute can provide short, relevant product highlights.

A strong description supports these fields but does not replace them.

Writing “GTIN 123…” inside a paragraph is not the same as supplying the value in the proper GTIN attribute.

Writing “colour: blue” in a description does not necessarily replace the colour attribute for a category where colour is required.

Handle product category differences

Title priorities vary by product type.

Apparel

Useful title elements can include:

• Brand
• Product type
• Gender or intended audience
• Material
• Important style
• Colour
• Size

Example:

Northbay Women’s Linen Midi Dress – Emerald Green – Size M

Electronics

Useful title elements can include:

• Brand
• Model
• Product type
• Capacity
• Key specification
• Colour

Example:

Voltix V20 Wireless Headphones – Bluetooth – Black

Do not include a technical standard unless the product genuinely supports it.

Replacement parts

Useful title elements can include:

• Manufacturer or brand
• Compatible model
• Part type
• Part number
• Important dimension

Example:

PureAir Replacement HEPA Filter for PA-300 – Part PF300

Compatibility claims must be verified. An incorrect compatibility statement can lead to customer dissatisfaction and product returns.

Furniture

Useful title elements can include:

• Brand
• Furniture type
• Material
• Style
• Colour
• Dimensions

Example:

Oakline Solid Oak Dining Table – Natural Finish – 160 × 90 cm

Food and packaged goods

Useful title elements can include:

• Brand
• Product type
• Flavour
• Quantity
• Net weight
• Pack count

Example:

GreenField Roasted Almonds – Unsalted – 500 g

Do not place health, treatment or nutritional claims in a title unless they are accurate, permitted and supported.

Bundles and multipacks

A title and description must make the package contents clear.

Examples:

Voltix USB-C Charging Cable – 2 m – Pack of 3

CameraPro C10 Camera Kit with 18–55 mm Lens and Carry Bag

A multipack of identical products is not necessarily the same as a bundle containing different products.

Use the applicable Merchant attributes in addition to accurate title and description wording.

Use language consistently

The language assigned to the product data should agree with the title, description and landing page.

Do not submit:

• An English title with a Turkish description
• A Turkish title linked to an English-only page
• Automatically translated attributes mixed with untranslated text
• A product title containing several languages for keyword coverage
• A description copied from a supplier in another target language

Brand names and universal model identifiers can remain unchanged.

Technical terms can also be used when they are the correct names of the product characteristics.

However, the full product presentation should remain understandable in the selected content language.

If the store targets several languages, maintain a complete product source and landing-page experience for each supported language rather than combining translations in one title.

Do not confuse capitalization with visibility

All-capital titles do not create reliable prominence.

Avoid:

ACME BEST WATERPROOF RUNNING SHOES BLACK SALE

Use:

Acme TrailPro Waterproof Running Shoes – Black

Capitalization should follow the language’s normal writing conventions.

Preserve legitimate brand capitalization where appropriate, but do not transform an entire title or description into uppercase text.

Also avoid excessive:

• Exclamation marks
• Decorative symbols
• Emoji
• Repeated punctuation
• Unnecessary trademark symbols
• Artificial spacing
• Non-standard characters

Treat automatically generated text carefully

Automated rules can help large WooCommerce catalogues, but the output must remain accurate for every product.

A rule such as:

{brand} {product_name} {color} {size}

can fail when:

• A brand is missing
• The product name already contains the brand
• The product is not a variable product
• The colour value is inherited incorrectly
• Size does not apply
• An attribute contains an internal code
• The rule exceeds the supported length
• The output repeats the same words

Before applying a bulk rule:

1. Test simple products.
2. Test variable products.
3. Test products without brands.
4. Test products without optional attributes.
5. Test unusually long names.
6. Test multilingual products.
7. Test bundles and multipacks.
8. Test products with custom fields.
9. Preview the final title.
10. Review a representative catalogue sample manually.

Do not optimize thousands of products with an untested formula.

Disclose generative AI product text correctly

Google’s current product data specification distinguishes between standard human-authored text and product text created using generative AI.

For generative-AI titles, Google directs merchants to use the structured title [structured_title] attribute. For generative-AI descriptions, Google directs merchants to use the structured description [structured_description] attribute.

The relevant digital source type is:

trained_algorithmic_media

The normal title [title] and description [description] attributes remain appropriate for content that was not created using generative AI.

This distinction matters when a merchant uses AI to generate or substantially create product text.

Do not assume that every WooCommerce integration currently supports:

• structured_title
• structured_description
• digital_source_type
• trained_algorithmic_media

Confirm what the installed integration version can submit.

If a required structured attribute is unsupported, do not silently mislabel generated content as ordinary text. Establish an appropriate content and integration workflow before using generated titles or descriptions at scale.

AI-generated text must still be checked for:

• Invented features
• Incorrect materials
• False compatibility
• Wrong model numbers
• Unsupported performance claims
• Incorrect pack contents
• Wrong variation attributes
• Mixed languages
• Promotional statements
• Repeated catalogue text

AI generation does not transfer responsibility for product accuracy to the software.

Inspect structured product data

WooCommerce, the active theme, an SEO plugin and another commerce extension can each generate Product schema.

Compare the structured-data product name and description with:

• WooCommerce
• The visible landing page
• Submitted Merchant data
• The selected variation
• Merchant Center processed information

Look for:

• Duplicate Product objects
• Different product names
• Old descriptions
• Parent-product data applied to a variation
• Incorrect brand
• Wrong SKU
• Wrong variation attributes
• Cached sale language
• Another-language description
• Description content from an inactive plugin

Structured data does not need to serve as the Merchant submission source to create contradictory public evidence.

Resolve the authoritative schema output instead of adding another Product object.

Prevent old sources from restoring previous titles

A WooCommerce product can be represented by several Merchant Center sources:

• Merchant API
• A previous Content API integration
• XML data source
• Scheduled file
• Ecommerce-platform connection
• Automatically found products
• Supplemental source
• Manual product entry
• Merchant Center attribute rule
• Manual Merchant Center edit

After optimizing a title or description, determine whether another source can overwrite it.

Record:

• Data-source name
• Data-source type
• Last update
• Offer ID
• Language
• Feed label
• Target countries
• Submitted title
• Processed title
• Submitted description
• Processed description

Do not delete a data source merely because it contains older text. First identify its role and whether other required product information depends on it.

Verify Merchant API processing

The Merchant API represents title and description as product attributes within product information. Google’s current Merchant API ProductAttributes reference includes standard title and description fields as well as structured title and structured description fields.

After making a WooCommerce correction:

1. Confirm the public product page.
2. Clear relevant caches.
3. Run the supported product update.
4. Record the operation time.
5. Record the data source.
6. Record the offer ID.
7. Check whether the operation succeeded.
8. Allow Merchant Center to process the input.
9. Retrieve or inspect the processed product.
10. Compare the processed title and description.
11. Review item-level issues.
12. Review the applicable destination and country.

A successful submission response does not prove that Google has processed or accepted every supplied value.

Google’s Merchant API product-status guidance explains that processed product status can include destination status and item-level issues.

Treat submission, processing and eligibility as separate results.

Measure optimization without making uncontrolled changes

Do not change every product title repeatedly over short periods.

Frequent unrecorded changes make it difficult to understand:

• Which wording Google processed
• Which title was active during a performance period
• Whether a variation was differentiated
• Whether a source overwrote the change
• Whether performance changed for another reason

Create a controlled record containing:

• Product ID
• Offer ID
• Original title
• New title
• Original description
• New description
• Reason for change
• Date submitted
• Date processed
• Country
• Marketing method
• Product status
• Relevant performance period

Performance can be influenced by many factors beyond title and description, including:

• Search demand
• Competition
• Price
• availability
• Reviews
• Promotions
• Product images
• campaign settings
• Bids and budgets
• Seasonality
• Account eligibility

Do not attribute every performance change to wording alone.

What PW Merchant API can support

PW Merchant API supports an API-oriented WooCommerce and Google Merchant Center product workflow.

Depending on the installed version, configured mappings and connected account, it can help merchants:

• Review WooCommerce product information.
• Identify products requiring attention.
• Work with simple products and variations.
• Prepare supported product attributes.
• Preserve controlled offer identities.
• Submit supported product updates.
• Schedule product synchronization.
• Record applicable operation results.
• Display supported product issues.
• Compare WooCommerce information with applicable Merchant results.

These functions can support title and description correction by helping the merchant determine whether updated WooCommerce product information reached Google.

PW Merchant API cannot independently:

• Write accurate product information without reliable source data.
• Confirm an unsupported product claim.
• Determine legal advertising requirements.
• Guarantee product approval.
• Guarantee impressions or clicks.
• Guarantee sales.
• Override Google’s product-data rules.
• Correct contradictory public-page content.
• Remove competing data sources automatically in every configuration.
• Guarantee that every generated title improves performance.
• Replace manual review of bulk-generated text.
• Decide whether a generative-AI disclosure is unnecessary.
• Guarantee support for every new Merchant attribute in every installed version.

WooCommerce remains the merchant’s commercial product source. PW Merchant API supports applicable product communication, and Google independently processes and evaluates the resulting information.

Common title and description optimization mistakes

Adding every possible keyword

A product title should identify the item rather than list search queries.

Copying one title across all variations

Separately submitted variations need sufficient distinguishing information.

Changing only the SEO title

The Merchant integration may use the WooCommerce product name or another mapped field.

Changing only Merchant Center manually

The next WooCommerce synchronization can restore the old value.

Using supplier descriptions without review

Supplier text can contain another company’s identity, incorrect availability, outdated specifications or unsupported claims.

Adding promotional language

Shipping, discounts and sales messages do not belong in standard product titles or descriptions.

Hiding an inaccurate variation behind a generic title

A generic parent title does not correct the wrong colour, size, image or landing-page selection.

Writing for search engines instead of customers

Unreadable repetition reduces clarity and can create policy or data-quality problems.

Ignoring the landing page

Submitted wording must remain supported by what customers see.

Ignoring structured data

Old schema output can contradict corrected WooCommerce and Merchant information.

Editing thousands of products without testing

A bulk formula can repeat brands, add blank separators or apply irrelevant attributes across the catalogue.

Assuming 150 characters must always be used

The title limit is a maximum, not a mandatory target.

Filling descriptions to 5,000 characters

Length does not compensate for irrelevant or repeated information.

Using AI-generated text without validation

Generated descriptions can invent features, compatibility, materials and product benefits.

Ignoring AI source classification

Google provides structured title and description attributes for generative-AI product text.

Frequently asked questions

What is the maximum Google Merchant product title length?

Google’s product data specification allows up to 150 characters for the title attribute. The entire title may not be displayed, so place important identifying information early.

Should every WooCommerce product title use all 150 characters?

No. Use only the space needed to identify the product accurately. Do not add irrelevant words to reach the maximum.

What is the maximum product description length?

Google permits descriptions up to 5,000 characters. Google also recommends approximately 500–1,000 characters in its guidance for descriptions considered too short, but the appropriate length depends on the product.

Should the Merchant title be identical to the WooCommerce product name?

The submitted title should agree with the landing page and describe the same product. A mapped Merchant-specific title may contain additional accurate identifying details, but it should not contradict the public product page.

Is the WooCommerce SEO title used by Google Merchant Center?

Not automatically. The active integration determines which field is mapped. Check the submitted and processed product rather than assuming the SEO title is used.

Should the short or long WooCommerce description be submitted?

That depends on the integration mapping. Identify the field used by the current data source and confirm the processed Merchant description.

Can I add search keywords that do not appear on the product page?

Google advises merchants to keep submitted titles and descriptions aligned with landing-page content and not add unrelated synonyms or search terms that are absent from the page.

Can I include “free shipping” in the title?

No. Google identifies promotional text such as “free shipping” as unsuitable for the standard title and description attributes.

Can I include the price in a product title?

Normally, price belongs in the price attribute and on the landing page. Adding changing price information to the title can create outdated or contradictory text.

Should brand always appear first?

Not necessarily. The most effective truthful order depends on the product category and how customers identify the item. Brand is often important, but it should not displace more essential product identity without a reason.

Should variation colour and size appear in the title?

When colour, size or another attribute distinguishes a separately submitted variation, including it can make the offer clearer. The value must match the variation and landing page.

Can all variations use the parent description?

They can share factual common information, but variation-specific differences must remain correct. Do not let a shared description state the wrong colour, material, capacity or included item.

Should GTIN be written inside the description?

A GTIN should be supplied through the appropriate GTIN attribute when available and applicable. Mentioning it only in the description does not replace the structured attribute.

Can I use the manufacturer’s description?

Only after confirming that the merchant is authorised to use it and that it accurately describes the exact product. Remove unrelated company information, unsupported claims and references to unavailable accessories.

Can AI write WooCommerce product titles and descriptions?

AI can assist, but every output must be validated against reliable product information. Google provides structured title and structured description attributes for generative-AI text, so the submission workflow must also handle the applicable source classification.

Does PW Merchant API automatically optimize every title?

Do not assume that it automatically rewrites every product. Its applicable functions depend on the installed version and configured workflow. The merchant remains responsible for product accuracy and final review.

Will an optimized title guarantee more clicks?

No. It can improve product clarity and relevance, but performance also depends on demand, competition, price, images, eligibility, reviews, campaigns and other factors.

Why does Merchant Center still show the old title?

The update may still be processing, the operation may have failed, a cache may expose old content or another data source or rule may control the value.

Can I edit the title directly in Merchant Center?

Manual edits may be available in some workflows, but they can be overwritten by the authoritative WooCommerce source. Make durable corrections in the source that will continue controlling the product.

Do title changes require a review request?

Normally, corrected product information is submitted and reprocessed. A manual account review should not be requested merely because a title was edited unless the exact issue specifically requires that action.

Should every product description be unique?

Every description should accurately represent its product. Closely related variations can share common factual content, but unrelated products should not receive generic duplicated descriptions that fail to identify them.

Final optimization checklist

Before submitting optimized titles and descriptions, confirm that:

• The correct WooCommerce product was selected.
• The correct variation was selected.
• The WooCommerce product ID was recorded.
• The variation ID was recorded where applicable.
• The SKU was checked.
• The Merchant offer ID was checked.
• The active data source was identified.
• The actual title source field was identified.
• The actual description source field was identified.
• SEO and Merchant fields were not confused.
• The title identifies the real product.
• The title is within the supported limit.
• Important product information appears early.
• Brand information is accurate.
• Model information is accurate.
• Product type is accurate.
• Variation attributes are accurate.
• Colour matches the product.
• Size matches the product.
• Material matches the product.
• Capacity matches the product.
• Pack quantity matches the product.
• Compatibility claims are verified.
• Product condition is accurate.
• Bundle contents are accurate.
• The title does not contain promotional text.
• The title does not contain keyword lists.
• The title does not contain unsupported superlatives.
• The title does not contain unnecessary capital letters.
• The title does not contain gimmicky characters.
• Each separately submitted product is distinguishable.
• Variation titles follow one consistent structure.
• The description explains the product itself.
• The description is within the supported limit.
• Important description details appear early.
• The description uses natural language.
• The description does not repeat search phrases.
• The description does not contain store links.
• The description does not contain payment instructions.
• The description does not contain shipping promotions.
• The description does not compare competitors.
• The description does not advertise unrelated products.
• The description does not contain broken shortcodes.
• Page-builder residue has been removed.
• Supplier text has been reviewed.
• Legal and medical claims have been reviewed where relevant.
• GTIN is supplied through the appropriate attribute.
• Brand is supplied through the appropriate attribute.
• MPN is supplied through the appropriate attribute.
• Colour and size are supplied through appropriate attributes.
• Product details are structured where applicable.
• Product highlights are structured where applicable.
• The selected content language is consistent.
• The landing page uses the same language.
• The landing page describes the same product.
• The landing page represents the submitted variation.
• The public product name supports the submitted title.
• The public description supports the submitted description.
• Structured product data was inspected.
• Duplicate Product schema was investigated.
• Structured-data names are accurate.
• Structured-data descriptions are accurate.
• AI-generated content has been identified.
• AI-generated content has been manually verified.
• Applicable structured AI attributes are supported.
• The appropriate digital source type is supplied.
• Bulk rules were tested on simple products.
• Bulk rules were tested on variable products.
• Bulk rules were tested on products with missing attributes.
• Bulk rules were tested on long product names.
• Blank or repeated separators were removed.
• Competing data sources were identified.
• Merchant Center rules were reviewed.
• Manual Merchant edits were reviewed.
• Automatically found products were reviewed.
• Relevant WordPress caches were cleared.
• Relevant server caches were cleared.
• Relevant CDN caches were cleared.
• The public page was tested while logged out.
• The corrected product was submitted.
• The operation result was recorded.
• Rejected operations were investigated.
• Merchant Center processed the new title.
• Merchant Center processed the new description.
• Item-level issues were reviewed.
• Country status was reviewed.
• Marketing-method status was reviewed.
• The optimization date was recorded.
• Performance comparisons use a stable time period.
• No approval or performance guarantee is claimed.

WooCommerce product title and description optimization should begin with product identity and end with processed Merchant Center verification.

The title must tell customers and Google what the product is. The description must explain the product’s relevant characteristics without becoming a keyword list, company profile or promotional message.

Every separately submitted variation should remain distinguishable. Brand, model, colour, size, material, capacity and compatibility information must be supported by the actual WooCommerce product and public landing page.

The merchant must also identify which WooCommerce fields the integration uses. Changing an SEO title, short description or manual Merchant value is ineffective when another field or data source remains authoritative.

After a correction, the merchant should clear relevant caches, submit the supported update and inspect the processed Merchant information. A successful operation does not by itself prove that the new title or description has been processed or that the product is eligible.

PW Merchant API can support product review, controlled WooCommerce product communication, variation handling, operation results and applicable Merchant issue visibility. It cannot create missing product truth, guarantee approval or ensure that every rewritten title improves performance.

Accurate titles and descriptions create a clearer relationship between the WooCommerce catalogue, the public product page, Merchant API product information and Google Merchant Center.

That consistency is more sustainable than keyword repetition, temporary manual edits or unverified bulk-generated content.