# Custom advanced parsers

In some cases, default parsers may not be sufficient—for example, when a website doesn't use a standard product schema or if you need full product details such as specifications, short descriptions, or image galleries. Product variations are also not supported by default parsers. For these scenarios, we offer custom advanced parsers tailored to your specific needs.

### Request a Custom Parser

Our team can develop advanced, site-specific parsers upon request.

#### Pricing

| Parser Type                                                                                                                     | Price    |
| ------------------------------------------------------------------------------------------------------------------------------- | -------- |
| Websites **without a product schema** or requiring additional fields (e.g., gallery images, specifications, short descriptions) | $50      |
| Websites with **dynamic content** rendered via JavaScript                                                                       | from $50 |
| **Supplier websites** that require authentication (login/password) to access product data or pricing                            | from $50 |
| Stores with **product variations** (e.g., color, size options)                                                                  | from $50 |

> **Note:** Final pricing may vary based on site complexity. Please send us the list of websites for a custom quote.

#### How to Request a Parser

1. **Contact Support**\
   Email [our support team](https://www.keywordrush.com/contact) with your parser request.
2. **Provide Site Links**\
   Include the URLs of the websites you want us to support.
3. **Turnaround Time**\
   Most custom parsers are completed within **1–2 business days**.

#### What’s Included

* Extraction of all standard and extended product fields, where available
* A **6-month warranty** on each custom parser. If the site changes during this period, we’ll update your parser at no additional cost.

### FAQs

**Will my parser work for all websites?**\
No. Each website has its own unique layout and data structure. A separate parser is required for each individual site.

**Will my custom parser be shared with other users?**\
No. Your custom parser will not be included in the public plugin distribution.

**What if the website changes and my parser stops working?**\
We provide **free support and updates** for a period of **6 months** after delivery. If the site structure changes during that time, we’ll update your parser at no additional cost.

### **Create Your Own Parser**

If you have basic PHP and XPath skills, you can [create advanced parsers](https://ei-docs.keywordrush.com/for-developers/custom-parsers) for the stores you need.

### **Installing Custom Parsers**

Custom parsers are delivered as PHP files. To install them on your website, follow these steps:

1. **Create Directory**: Use a file manager plugin, file manager in your hosting panel, or an FTP client to create the directory:

```
/wp-content/ei-parsers
```

2. **Copy Files**: Copy the provided parser files to this directory.

Installation is now complete.

{% hint style="success" %}
Custom parsers work the same as default parsers. You can safely update the plugin or WordPress; the directory with custom parsers won't be overwritten.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ei-docs.keywordrush.com/extracting-products/custom-advanced-parsers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.