Guide
How-to guide
Generate and validate one Merchant Center attribute rule in three steps: describe the need → generate the rule → review & apply. Details for each step below.
Describe the need
Tell RuleGen the result you want in plain English — e.g. "if the product title is missing the brand, prepend the brand to the title." No rule syntax required.
Generate the rule
The system parses your sentence into a structured rule model (target attribute + condition + operation), and lists its assumptions and confidence so a guess is never treated as a fact.
Review & apply
Simulate Before/After locally. Once it passes validation, copy the rule spec and drop it into Merchant Center following the application guide. Publishing always stays in your hands.
Supported operations
The MVP supports these 6 operations, composeable inside conditional logic. A rule chain can link up to 5 sequential operations.
| Operation | Code | Description |
|---|---|---|
| Set To | set | Set the target attribute directly to a value or a {{field}} template. |
| Prepend | prepend | Add the given content to the front of the target attribute’s current value. |
| Append | append | Add the given content to the end of the target attribute’s current value. |
| Find & Replace | replace | Find and replace a substring; supports case options and global replace. |
| Clear | clear | Empty the target attribute. |
| Conditional Logic | conditions | Decide whether the rule fires based on condition fields (e.g. brand is not empty, title does not contain brand). |
Application boundary
RuleGen never connects to a Google account and never auto-publishes rules. "Ready to apply" only means the rule passed against the sample data you provided; final validation and publishing still happen in Merchant Center.