After registering and setting up your developer account, you can submit your extension to the Chrome Web Store. But before you do so, there are a few ways to prepare your extension and other content before submitting your item.
Test your extension in production
Load your extension locally and make sure all your features work as intended before uploading your extension to the Chrome Web Store.
Review your manifest
After uploading your item, you won't be able to edit the metadata of your manifest in the developer dashboard. This means, that if you notice a typo, you will have to edit the manifest, increase the version number, and zip the files all over again.
Make sure you check and include the following fields:
"name"- This name appears in the Chrome Web Store and the Chrome browser.
"version"- The version number of this extension release.
"icons"- An array specifying the icons of your extension.
"description"- A string of no more than 132 characters that describes your extension.
Set the initial version number in the manifest to a low value, such as 0.0.0.1. That way, you have room to increase the version number when you upload new versions of your item. Each new version that you upload to the Chrome Web Store must have a larger version number than the previous version.
Zip your extension files
To upload your extension, you need to submit a ZIP file that contains all extension files. Make sure you place the manifest file in the root directory, not in a folder.
Additional store listing content
Besides the metadata in your manifest, you will also need to provide content, images, and URLs that will help your users understand what value your extension offers. See Creating a great listing page for details on creating a high-quality listing page that clearly communicates what your item will offer, using the item description, images, and other listing metadata.