# Prepare extension for submission
To publish your extension to the Chrome Webstore follow the steps in the [Chrome Developer Docs](https://developer.chrome.com/docs/webstore/publish/). But let’s tidy your extension up before doing so:
1. Open `manifest.json` in any text editor and adjust the app name and description in line 3 and 4
2. Make sure to delete the content script section from `manifest.json` if you don’t use any content scripts in your extension. Otherwise your extension might be rejected by Google. 
3. Delete unused permissions from the `manifest.json` file. EG if you don’t use the Chrome local storage workflows in your extension, delete the line "storage", in manifest.json. You will most likely always need activeTab and scripting. Once you delete any permissions, please test if you app still works correctly.
4. If you have a square icon for your Chrome extension, use an online resizing service (e.g. ) and replace the files in the images folder. Make sure to keep the names as is (i.e. 16x16.png, etc.).
5. If you don’t need microphone access from your sidebar, please comment out (i.e. add // in front of the line) lines 168, 253 and 301 in `background.js`
---
# 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://cranford-tech.gitbook.io/charles/publishing-to-the-chrome-webstore/prepare-extension-for-submission.md?ask=
```
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.